pfsweb.com website review

Your mobile performance score is 99 (desktop: 100). That is in Google's “good” band (90 and up).

A phone's processor spends 0.3 s on main-thread work while loading, 48 ms of it running JavaScript. That is comfortably low.

Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

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

Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 661 ms for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Play video”.

The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

The page is fully interactive after 2.0 s.

The layout barely moves while loading (CLS 0.039, good is under 0.1).

Visually, the page fills in at 1.1 s (Speed Index), inside the 3.4 s “good” threshold.

Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Your homepage downloads 417 KiB in 13 requests on a phone: fonts 211 KiB (3), images 129 KiB (7) and HTML 63 KiB (1). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

Images below the first screen wait until the visitor scrolls to them.

No image is downloaded at more than three times the size it is drawn on a phone.

All 21 images in the HTML carry an alt attribute.

axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

Your meta description is 158 characters: “GXO is creating game-changing opportunities with our ever evolving logistics and supply chain management. Learn more ab…”.

Your main headline reads: “Discover logistics at full potential.”.

The canonical URL is https://gxo.com/.

Open Graph tags are complete, so shared links show a title, description and image.

Your server sends the page's text in the HTML (1,197 words), so crawlers that don't run JavaScript still read it.

The site publishes https://gxo.com/llms.txt (141 KiB, 532 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

All 15 pages we checked loaded without an error.

No page we checked hands its ranking to a different URL.

All 15 pages that loaded have a meta description.

Every page we checked has its own title.

Each page we checked has a main headline.

None of the pages we checked carries a noindex tag.

All 15 pages that loaded have a <title>.

The page declares a mobile viewport.

The homepage has 3 calls to action, for example “Contact us” and “Subscribe”.

2 short forms (4 fields at most) are right on the homepage, asking for an email.

Analytics detected: Google Tag Manager.

No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).