Site AI Auditمن Internet Solutions

Slow Pages Finding: Which Pages Took Over Two Seconds

١٨ نوفمبر ٢٠٢٦وقت القراءة: 8 دسرعة الموقع
Slow Pages Finding: Which Pages Took Over Two Seconds

Short answer: While Site AI Audit crawls your website, it times every page it opens. If a page takes more than 2 seconds to load, it goes into a notice called “Pages that took over 2 seconds to load”. Unlike the Google speed score, which looks at your home page, this finding shows individual pages deep inside the site, such as category pages, search results and old posts. The usual fix is caching, or removing what makes that kind of page heavy.

Two kinds of speed information in one report

The speed area of the report combines two views. The first is the Google PageSpeed measurement of the home page on a phone: the mobile score, the main content time, the layout shifts. That tells you how the front door performs. The second is the timing that the crawler records for every other page while it walks through the site. That tells you about the rooms behind the door, which visitors reach from search and from links.

The slow pages finding comes from the second view. It is a notice, the lowest severity, but it carries information that the home page measurement cannot give: a site can have a fast home page and a slow section that frustrates every visitor who lands on it. Many sites have exactly this pattern.

What the finding says

The finding is titled “Pages that took over 2 seconds to load”. The explanation says that slow pages lose visitors and crawl budget, and the advice is to check caching and heavy content on these pages. The report lists the pages that crossed the threshold, so you can see which parts of your site are slow instead of guessing.

The number is the time the page took to arrive during the crawl, measured from the audit’s server. The crawler is polite, at about three requests per second, so it does not overload your site, and the numbers reflect normal conditions. One slow page may be a fluke. A list of twenty pages from the same section is a pattern.

A related warning: pages that did not respond

A more serious cousin sits in the SEO area: “Pages that did not respond”, a warning. These are pages that timed out or refused the connection during the check. If a page is so slow that it never answers, it appears there instead. When you see both findings, start with the pages that did not respond, since they fail completely. The cause is usually an overloaded server or a page that runs a very expensive operation. The guide on resource limit and 508 errors on shared hosting covers one common reason.

Why individual pages are slow

A single slow page usually has a specific reason. The common ones are:

How to find the pattern

Do not treat the list as individual problems. Sort the addresses by type. If most of them share a folder or a parameter, such as /search or ?filter, the cause is the template or the query behind that section. If they are old posts with many images, the cause is content weight. If they are scattered randomly, the cause may be the server being busy while the crawler visited. Re-check a few pages in your browser’s network panel and look at the waiting time. If the waiting time, the time before the first byte arrives, is long, the problem is on the server. If the download takes long, the problem is page size.

What to do about each pattern

  1. Server-side waiting time is long. Turn on page caching, extend it to the affected section where safe and consider upgrading hosting. See how to reduce server response time.
  2. Search and filter pages. Cache them for a short time, limit the number of results per page and make sure the database has the right indexes. For WordPress, fixing slow WordPress search covers common options.
  3. Heavy pages. Compress and resize images, load embeds only when the visitor asks for them, and remove widgets that the page does not need.
  4. Calls to external services. Cache the result locally or load the widget after the page, so the page does not wait.
  5. Whole section slow. Look at the template. A single expensive loop in a theme can slow every page of that type.

Do you need to fix all of them?

No. The finding is a notice, and the right response depends on how many visitors the slow pages get. A slow page that gets hundreds of visits a day, such as a main category, is worth fixing at once. A slow page from an old post that nobody reads can wait, or be merged or removed, as described in the article on content audits. Use your analytics to see which slow pages matter. The crawl-time list tells you where the problems are, and your own traffic data tells you which of them are worth your time.

Crawl budget: the search engine side

The explanation also mentions crawl budget. Search engines do not crawl every page of every site every day; they allocate effort based on how fast and healthy a site is. If many pages are slow, crawlers visit fewer pages, and new content is discovered later. For a small site this is rarely a problem, but for a shop with thousands of pages it can delay the appearance of new products in search. The article on crawl budget explains when it matters.

Measuring the effect of a fix

The list is also a handy before-and-after tool. Note how many pages were on it, and which ones, then run the check again after the fix. A shorter list, or a list in which the slowest pages are no longer there, is clear proof. If the same pages are still listed, the fix did not reach them: perhaps the cache excludes them, or a different rule applies. Because each check uses the same method, the lists are comparable, and a gradual improvement over several checks tells you that the work is going in the right direction.

Do not forget images and downloads

Pages are sometimes slow for a simple reason: they contain very large files. A single unoptimised photograph or a document embedded in a page can add seconds on a normal connection. When you open a slow page in the network panel and sort by size, the culprit is usually obvious. Replacing it with a properly sized version often fixes the page in a few minutes, with no technical change at all.

A worked example

An outdoor equipment shop has a fast home page and a mobile score in the eighties. The audit shows a notice: 34 pages took over 2 seconds to load. The list shows that 31 of them are category pages with filter parameters, such as pages filtered by size and colour. The developer finds that these pages are excluded from the page cache and run a heavy query for every request. He adds short-lived caching for filtered pages, limits the number of options that can be combined and adds a missing database index. A new check shows only three slow pages, which turn out to be large blog posts with embedded videos. He replaces the embeds with thumbnails that load the video on click. The notice disappears, and the category pages feel faster to shoppers.

To see which of your pages are slow, check your website with Site AI Audit. The check needs a free account; the plans unlock the full report with the list of pages.

Related reading

The bottom line

The slow pages notice shows the parts of your site that are slow even when the home page is fast. Look for the pattern, fix the cause for the pages that get the most visits and run the check again to confirm the list has shrunk.

الأسئلة الشائعة

How is this different from the Google speed score?

The Google score measures the home page on a phone. This finding comes from the crawler’s timing of all the other pages.

Is two seconds a strict limit?

It is the threshold for this notice. Pages that take longer are listed. It is a guide for where to look, not a ranking rule.

Why might a page be slow only during the audit?

The server may have been busy, or the page may not have been cached on the first visit. Check the list for patterns before acting.

Can the crawler slow my site down?

No. It makes about three requests per second and follows your robots.txt rules.

Should I fix every slow page?

No. Start with the pages that get the most visitors and the patterns that affect many pages at once.

#Page speed#Troubleshooting#Web hosting
افحص موقعك الخاص.هل موقعك محمي من الاختراق؟
افحص موقعي

المزيد من المدونة

كل المقالات ←
Internet Solutions

المزيد من فريقنا

من تطوير Internet Solutions. جرّب بقية منتجاتنا — كل منها يوفّر وقتك بطريقة مختلفة.

internet-solutions.net ↗
01النشر التلقائي على وسائل التواصل
PostRSS

تنتقل المنشورات الجديدة من خلاصة RSS الخاصة بك تلقائيًا إلى Facebook وX وLinkedIn وTelegram وأكثر من 60 شبكة أخرى.

خطة مجانية · منذ 2014زيارة ←
02دردشة مباشرة بالذكاء الاصطناعي للمواقع
Talkmio

يجيب موقعك على الزوار على مدار الساعة من محتواك أنت وبلغتهم.

خطة مجانية · دون بطاقةزيارة ←
03مساعد بالذكاء الاصطناعي
Ask Mio

دردشة وبرمجة وتصميم وكتابة وبحث. يختار Mio أفضل نموذج لكل مهمة.

خطة مجانيةزيارة ←
04طيار آلي بالذكاء الاصطناعي للمدونة ووسائل التواصل
AI Blog Autopilot

يكتب الذكاء الاصطناعي مقالات SEO من 2000 إلى 3000 كلمة وينشر كل مقال على أكثر من 60 شبكة اجتماعية.

أول 3 مقالات مجانًازيارة ←
05زحف SEO متعمّق
Site SEO AI Audit

زحف SEO كامل عبر 7 مجالات، بما فيها الظهور في البحث بالذكاء الاصطناعي، مع إصلاحات مرتّبة حسب التأثير.

من 12 € شهريًازيارة ←
06خلاصات RSS والمنتجات
RSS Feed Creator

أنشئ RSS من أي صفحة ويب، بالإضافة إلى خلاصات منتجات لـ Google وMeta تتحدّث تلقائيًا.

خطة مجانيةزيارة ←
07تطوير المواقع وتحسين محركات البحث
Internet Solutions

مواقع ومتاجر إلكترونية وأنظمة مخصّصة، يصمّمها فريقنا ويبنيها ويديرها.

منذ 2011زيارة ←