Website Speed Test and Page Speed Report
Website speed test for mobile and desktop using Google PageSpeed: Core Web Vitals, page weight and the biggest fixes. 2 credits per run.
A slow page costs you visitors before they read a word. People tap a result, wait, and go back. If you pay for ads, that wait also means you paid for a click that never saw your offer. Most owners know their site feels slow on a phone, but few know which part is slow or what to change first.
The Page Speed Report from Dynamic Growth is an automated service. It costs 2 credits and needs only your website URL. Our software runs Google PageSpeed Insights on your page twice, once as a mobile phone and once as a desktop computer. The report shows the main lab timings (LCP, CLS, TBT, FCP and speed index), the real-user data Google holds for your site when it has any, the total weight of the page, and the biggest fixes with the time each one could save. You can start with the free 7-day trial, which comes with 1 credit and costs nothing for 7 days.
What you get
Real mobile and desktop speed measurements, what slows the page down and how to fix it.
Mobile and desktop results side by side
The page is tested as a phone and as a desktop computer, and the two sets of results sit next to each other. You can see at a glance whether the problem is limited to phones or affects every visitor.
Lab timings for each run
Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Total Blocking Time (TBT), First Contentful Paint (FCP) and speed index, each with its value and a plain label showing whether it sits in the good, needs improvement or poor range. These are measured in a controlled test, so they are a consistent way to compare one version of your page with the next.
Real-user data when Google has it
Google collects timing data from real Chrome visitors on sites with enough traffic. When that data exists for your page or site, the report includes it. When it does not, the report says so and leaves the section empty.
Page weight breakdown
The total size of the page and what it is made of, such as images, scripts, stylesheets and fonts. Heavy pages are slower on mobile data, and the breakdown shows which type of file is responsible.
Biggest fixes with estimated savings
A ranked list of the changes Google expects to help most, such as compressing images, removing unused code or cutting render-blocking files, each with an estimated saving. The estimates come from Google's own tool and show which fix to do first. The exact result will differ.
A report to download
The full report is saved in your dashboard. Download it to keep a record, compare it with a later run, or send it to the developer making the changes.
What we need from you
Your website URL.
- Mobile and desktop results
- LCP, CLS, TBT, FCP and speed index
- Real-user data when Google has it
- Page weight and the biggest fixes with estimated savings
Why page speed matters
Speed affects what a visitor sees and when. A page that shows its main content quickly and does not jump around while loading feels reliable. A page that stalls, shifts or ignores taps feels broken, even when the content is good. Google measures this with a small set of numbers called Core Web Vitals, and it uses them as one of the signals when it ranks pages. They are one signal among many. A fast page will not rank on speed alone, though a very slow one hands a competitor an easy edge.
Phones are where most sites lose. A page that loads well on an office computer and fast wifi can crawl on a mid-range phone over a mobile connection. That is why the report tests both. The mobile run is the stricter one, and it is usually the one that shows the real problems: oversized images, scripts that block the page, and fonts or widgets that load late.
Speed problems also tend to come from a short list of causes. A few uncompressed photos, a chat widget, three tracking scripts and a heavy theme can account for most of the delay. A report that names those items and estimates what removing each would save is more useful than a score alone, because you can fix the largest one first and test again.
How it works
Enter your website URL
Type the address of the page you want tested and confirm the run. It costs 2 credits and needs no uploads, no code on your site and no access to your accounts. Pick the page that matters most, such as your homepage or the page your ads point to.
Automatic testing on mobile and desktop
Our software requests Google PageSpeed Insights for your page with a phone profile, then with a desktop profile, and collects the timings, page weight, any real-user data and the suggested fixes.
Read the report
The report appears in your dashboard. Start with the mobile timings, then read the list of fixes from the top. The largest estimated savings are listed first.
Apply the fixes yourself
Make the changes in your CMS, theme or code, or hand the list to a developer. Once they are live, run the report again to see the difference.
Common speed problems the report finds
Images that are larger than they need to be
A photo uploaded straight from a camera can be several megabytes, and it is then shown in a space a few hundred pixels wide. Resize the image to the size it is displayed at, save it in a modern format such as WebP, and the page gets lighter right away.
Scripts that block the page
Some scripts must finish loading before the browser can show anything. Tracking tags, chat widgets and sliders are common causes. The report lists the ones that delay the first view, so you can remove those you no longer use and defer the rest.
Layout that jumps while loading
If an image has no set size or a banner loads late and pushes the text down, the page shifts under the visitor's finger. This is what CLS measures. Setting width and height on images and reserving space for banners usually fixes it.
Unused code
Themes and plugins often load stylesheets and scripts for features the page never uses. The report shows how much of each file goes unused, so you can remove or trim what you do not need.
Slow server response
If the server takes a long time to start sending the page, everything after it waits. Cheap hosting, no caching and heavy page builders are frequent causes. The report flags a slow first response, though it cannot see inside your server to say why.
What the report measures
- Largest Contentful Paint (LCP). How long it takes for the largest visible element, usually a hero image or main heading, to appear. It is the closest of the numbers to how fast the page feels to a visitor.
- Cumulative Layout Shift (CLS). How much the page content moves around as it loads. A low score means the layout stays put. A high score means visitors may tap the wrong thing as elements jump.
- Total Blocking Time (TBT). How long the page is too busy running scripts to respond to a tap or a click. In lab tests it stands in for the responsiveness that real visitors feel.
- First Contentful Paint (FCP). How long before the first text or image shows up. It tells you when the screen stops being blank.
- Speed index. How quickly the visible part of the page fills in while loading. A lower number means the page looks complete sooner.
- Page weight. The total size of everything the page loads, split by file type. It helps explain why a page is slow on a mobile connection.
Do it yourself or run the report?
You can run PageSpeed Insights yourself at no cost. Paste a URL into Google's tool and read the result. If you are comfortable with the terms and want to test many pages, that is a fair way to work, and Chrome's built-in developer tools go further for someone who knows how to use them.
The Page Speed Report suits owners who want the result written up without having to interpret the raw output. It runs both device types, pulls out the numbers that matter, ranks the fixes and keeps the report in your dashboard so you can compare runs over time. It tests one page per run, and the numbers can shift a little between runs because the test depends on network and server conditions at that moment. Treat a single result as an estimate and look at the trend across runs. It cannot see inside your hosting.
Who it's for
Best for
- Owners whose site feels slow on a phone and who want to know why
- Advertisers sending paid traffic to a landing page that may be losing visitors to load time
- Businesses that have just changed their theme, plugins or hosting and want a before and after
- Developers and freelancers who need a clear, ranked list of fixes to work from
Not the right fit if
- Anyone who wants the speed problems fixed for them, since the service only reports
- Pages behind a login, which the test cannot reach
- Teams that need continuous monitoring of server load or uptime, which this one-off report does not provide
A page speed test and website performance test in one report
The Page Speed Report is a page speed test and website performance test built on Google PageSpeed Insights. It runs mobile and desktop, reports the Core Web Vitals lab numbers and real-user data when Google has it, and lists the biggest fixes by time saved. A site speed test that only gives one score for one device hides most of this.
Speed matters for visitors on slower connections in every market, including the Gulf, Latin America and parts of Europe, so test the page your ads and search results send people to. Run it again after each fix to confirm the number moved.
Frequently asked questions
Which page does it test?
The URL you enter. It tests that single page, on mobile and on desktop. If you want to know about several pages, such as the homepage and a landing page, run the report once for each.
What does it cost?
2 credits per run. The software works from the public URL, so you connect no accounts and install nothing on your site.
What does the report use to measure speed?
It runs Google PageSpeed Insights, which tests your page in a controlled lab setting and also reports real-user data from Chrome visitors when Google has enough of it for your site.
Why does it say there is no real-user data?
Google publishes it only for pages and sites with enough visits, which newer and smaller sites often lack. The report then shows lab timings only and says the real-user data is missing.
Why do my numbers change between runs?
Small differences between runs are normal, since each test meets different network and server load. Compare the same page over several runs and start with the fixes that show the largest estimated savings.
Will the report fix my site?
No. It measures the page and lists what to change, and nothing on your site changes unless you or your developer change it. Treat the estimated savings as Google's projections.
How much does page speed report cost?
Page Speed Report costs 2 credits. On the Starter plan ($29 for 10 credits) that is about $5.80, on Growth ($59 for 25 credits) about $4.72, and on Scale ($129 for 60 credits) about $4.30. Ad spend is always paid separately to the ad platforms.
What do you need from me?
Your website URL.
Glossary
- Core Web Vitals
- A set of page experience measures from Google covering loading, visual stability and responsiveness. LCP, CLS and a responsiveness measure are the main ones.
- Lab data
- Results from a controlled test run by a tool. It is consistent and good for comparing changes, but it is not the same as what your real visitors experience.
- Real-user data
- Timings collected from actual Chrome visitors to your site. Google reports it only when there are enough visits.
- Render-blocking
- A file that the browser must download and process before it can show the page. Reducing these makes the first view appear sooner.