pagesix.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 211 ms

  211 ms

  Real visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) held steady for real visitors

  0%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 205 ms to 208 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 4.3 MB

  4.3 MB

  Your homepage downloads 4.3 MB on a phone, 1.1 MB of it images (25%). Under 2 MB keeps phones on slow connections fast.

• 1 image over 500 KB

  logos.png weighs 708 KiB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 1 image in older formats

  1 image (708 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  Elements (1)

• 1 image below the first screen load straight away

  1 image further down the page (30 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 1.2 g of CO₂ per visit

  1.22 g

  By the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

• Hidden but focusable

  3 elements hidden from screen readers can still receive keyboard focus.

  Elements (3)

• Frames without titles

  2 frames have no title, so screen-reader users cannot tell what they contain.

  Elements (2)

• 2 tap targets too small

  2 tap targets are too small or too close together to hit reliably with a finger.

  Elements (2)

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

• Heading levels should only increase by one (1 element)

  Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 72 links without text

  72 visible links have no text or label, so screen readers cannot say where they go.

  Elements (3)

• 2 form fields without a label

  2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  View source

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

• 210 internal links, 29 external

  The homepage links to 210 pages on pagesix.com and 29 external pages.

• robots.txt blocks 3 AI answer engine crawlers

  3 of 6

  Your robots.txt shuts out Claude search (Claude-SearchBot), Claude (Claude-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  View source

• No llms.txt

  There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• Opted out of AI training for 4 crawlers

  robots.txt blocks ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 99 found) and read each the way a search engine does.

• 5 JavaScript errors while loading

  5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• No call to action on the first screen

  On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  View source

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• About 279 words of copy

  The homepage carries about 279 words of visible text.

• 10 trackers load before any consent

  10

  Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 30 cookies set on arrival

  30

  Opening the homepage sets 30 cookies (measured from a US location before any click).

• 101 other companies contacted

  Loading the homepage contacts 101 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.