Find your slowest pages
with Response Time per Page
WebYes times how long each page takes to respond and charts them side by side, so the page that drags your site down has nowhere to hide.
- 3-days free trial
- No credit card required
- 4.9/5Average rating
- 5/5Average rating
Averages hide your slowest page
A healthy site average can conceal one page taking a hundred times longer than the rest. Per-page timing exposes it.
Every page, one chart
Each scanned page’s response time is charted side by side, so outliers are visible the moment the scan finishes.
Details on hover
Hover any bar to see the page title, exact response time, and full URL, so you know precisely which page to open.
The other half of speed
Core Web Vitals show how pages render. Response time shows how quickly they answer in the first place.
Spot the outlier, then dig in
Per-page timing turns “the site feels slow” into “this page is slow”.
One bar per page, slowest exposed
The chart lines up the response time of each page in your scan. When one page takes 0.779 seconds while the rest answer in milliseconds, you see it instantly, not after a customer complains.
- Response time charted for every scanned page
- Page title, time, and URL on hover
- Outliers stand out at a glance
Right beside your other vitals
Response time lives in the performance module with your Core Web Vitals and average response time trend, so slow answers and slow rendering get diagnosed in the same place.
- Lives in the performance dashboard
- Average response time tracked with trends
- One scan covers mobile and desktop
Time your pages in minutes
No installation, no code changes. WebYes scans your site from the outside.
Run a scan
Enter your URL and start a scan. WebYes times mobile and desktop in one pass.
Read the chart
Open the performance module and spot the bars that stand out from the rest.
Fix and re-scan
Speed up the slow page, re-scan, and confirm its bar shrinks back into line.
Which page is your slowest?
Response time per page is measured in every WebYes scan.
How long each page takes to respond when requested, measured in seconds during your scan. It captures the wait before anything starts rendering, which Core Web Vitals then pick up from.
Core Web Vitals measure how a page renders and behaves once it arrives. Response time measures how quickly it arrives at all. A page can render beautifully and still respond slowly, so you need both views.
No. WebYes times your pages from the outside during a scan. There is nothing to install and no code to add.
Common causes include heavy database queries, uncached templates, large third-party calls, or redirects. WebYes shows you which page is slow, so you know exactly where to start digging.
Yes. Every WebYes scan measures the response time of each scanned page alongside accessibility, SEO, quality, and the rest of the performance module. The free plan includes 10 scan credits.
