How to find websites with low PageSpeed Insight Score?

If you’re part of a web dev agency or a freelancer, finding websites with a low PageSpeed score can be an advantage.

Low PageSpeed scores are measurable, and a lot of clients like these scores since they give them a clear “score” of how their website is performing.

In this article, we will show you how you can find websites matching your exact Pagespeed score criteria.

How to find websites with low PageSpeed Scores?

This brief guide shows you how to identify websites with low PageSpeed scores.

1. Go to Stackcrawler.com: First thing, go to Stackcrawler.com.
2. Get a free account: You need a free account to filter websites by PageSpeed scores.
3. Navigate to a technology you want to check, such as WordPress websites, which is the most widely used content management system (CMS).
4. Filter by PageSpeed scores: Now you can filter by specific scores to only get websites that match your criteria.

What is Google Pagespeed Insight?

Google Pagespeed Insight is a test that runs on any website to measure its performance, accessibility, best practices and SEO.

Anyone can run a Pagespeed Insight test, even in your browser.

You can also check for performance tests, which provide information about the website’s performance.

Is Google PageSpeed scores important?

Absolutely, PageSpeed scores are important.

But there has been some misconception about it. Lots of SEOs and developers claim that having a good PageSpeed score correlates with a higher ranking.

The case is a bit more complicated.

Having good PageSpeed scores is particularly important when you already have some traffic, as it can significantly impact the website’s usability and performance.

Having a good user experience can result in a lower bounce rate.

Which in turn can result in a higher ranking.

However, it is a consensus that achieving a 100 on each test doesn’t inherently grant better rankings in search engines. It only increases the chances.

Better speed and performance can mean more conversions.

Imagine you’re visiting an e-commerce website for shoes. You go to two different websites, where one is fast and feels performant, while the other takes 3-4 seconds to load.

Unless it’s some terrific deals on the second store, users might prefer to use the faster ones, as it feels better for the user experience.

As a web developer myself, I tend to strive for all scores to be 100, which feels satisfying (and you get fireworks in the PageSpeed Console).

Also, when presenting to more non-technical people, getting 100 out of 100, a green number, and fireworks usually gets good credit.

How PageSpeed can affect websites

Lets us check the four pillars a PageSpeed audit consists of: 1) Performance, 2) Accessibilty, 3) Best Practices, and 4) SEO.

1) Performance

Audit	What it checks
Largest Contentful Paint (LCP)	Time until the biggest hero image or headline paints
First Contentful Paint (FCP)	First pixel of any text/image
Speed Index (SI)	Average visual-completion speed
Interaction to Next Paint (INP)	Worst interaction latency across the visit
Total Blocking Time (TBT)	Sum of long tasks that block input between FCP and TTI
Time to Interactive (TTI)	When the page is reliably usable
Cumulative Layout Shift (CLS)	Unexpected layout movement

2) Accessibilty

Audit	What it checks
Semantic structure & ARIA	Correct roles, required child roles, no aria-hidden focus traps
Text alternatives	Images/SVGs have descriptive alt/title text
Contrast ratio	Foreground/background meet WCAG thresholds
Keyboard & focus order	Buttons/links have accessible names, logical tab flow
Form labels & errors	Inputs are labelled and announce validation
Heading hierarchy / landmarks	Meaningful order for assistive-tech navigation

3) Best Practices

Audit	What it checks
Secure delivery	HTTPS on every request; prefers HTTP/2/3 for resources
Content-Security-Policy (CSP)	Strong enough to block XSS vectors
No deprecated APIs	Flags document.write(), synchronous XHR, etc.
No console errors	Runtime JS errors, mixed content, 404s
Media best practice	Correct image aspect ratios, lazy-load hints where appropriate
Passive event listeners, no blocking listeners	Smooth scrolling & gestures

4) SEO

Audit	What it checks
Meta viewport	<meta name="viewport" …> with width or initial-scale
Meta description	Non-empty <meta name="description">
Canonical link	Valid, absolute rel="canonical"
Hreflang	Proper language/region codes
Structured data valid	JSON-LD passes schema.org syntax
Legible font sizes	Text ≥ ~12 px for mobile
Tap-target size	Links/buttons large enough to tap
No legacy plugins	Page avoids Flash/Java, etc.