ubricHelp

What is a good server response time?

Rubric check: slow server response (check id speed)

Under 0.8 seconds is good, by Google's guidance for time to first byte (TTFB). Server response time is how long your server takes to start sending the page after it's asked. Over 1.8 seconds is slow.

Free, no card. Your report opens with this check first.

Why it matters for SEO

A slow first byte delays everything after it, including your Largest Contentful Paint, which is part of Google's Core Web Vitals. Google also crawls less of a site whose server answers slowly. One reading varies with network conditions, so re-test before you act on a single slow result.

Does this matter for ChatGPT and AI Overviews?

AI tools that fetch pages live have to wait for your server like anyone else, and some give up on slow pages, though their time limits aren't published. A fast response removes one reason a page might be skipped. The effect on citations hasn't been measured, so treat this as good practice, not a ranking lever.

How Rubric scores it

MinorMinor checks cost a quarter to a half of a standard check when they fail.

Why this tier: Server response time.

It is judged on every page Rubric scores.

Every Rubric score starts at 100. When this check fails, it takes up to 6 points off. Even one failing page costs at least 3 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 253 of 365 sites where Rubric could judge it (69%). That is 211 of 287 judged sites in Rubric's 313-site test set and 42 of 78 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Across those sites, about 1,655 of 12,588 pages were affected (13%). Measured 17 Nov 2026 with scoring 2026-v2.1.

69% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 1 of 1 times. (Engine build bbcec7c.)

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. Turn on page caching with your host's cache or a plugin such as WP Super Cache, W3 Total Cache or WP Rocket.
  2. Check for slow plugins: deactivate them one at a time on a staging copy and re-test with a tool such as PageSpeed Insights.
  3. Put a CDN in front of the site (many hosts include one), and move to a faster PHP version in your hosting panel if you're on an old one.

Shopify

Shopify hosts and caches the storefront for you, and there's no server setting to change. If it's slow:

  1. Remove apps you no longer use, since some add code that runs on every page.
  2. Simplify heavy Liquid in your theme, such as loops over large collections on the home page.
  3. Re-test a few times, since one reading can be off.

Webflow

Webflow serves published sites from its own CDN, and there's no server setting to change. Slow first bytes on Webflow are uncommon.

  1. Check whether a proxy or extra CDN on your domain sits in front of Webflow and adds delay.
  2. Re-test a few times, since one reading can be off.

Custom code

  1. Cache full pages at the server or CDN, so most requests don't run your app at all.
  2. Profile slow database queries and add indexes.
  3. Serve from a region close to your visitors, or use a CDN.

Check the time with curl -o /dev/null -s -w "%{time_starttransfer}\n" https://example.com/.

More page speed (lab) checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.