lavazzapro.co.uk website review

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

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

Your server sent the HTML in 217 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 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “A GLOBAL COFFEE BRAND LEADING COFFEE SOLUTIONS FOR YOUR WOR…”.

The page is fully interactive after 2.3 s.

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

Visually, the page fills in at 2.0 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 221 KiB in 29 requests on a phone: images 98 KiB (21), HTML 90 KiB (1) and stylesheets 22 KiB (4). 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 6 images in the HTML carry an alt attribute.

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

Your meta description is 133 characters: “Workplace vending solutions and quality coffee machines for your workplace. Unbeatable service, reliability & performan…”.

Your main headline reads: “Why Lavazza Professional”.

Your title is a healthy 62 characters: “Lavazza Professional UK - Workplace vending and coffee experts”.

The canonical URL is https://www.lavazzapro.co.uk/.

Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

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

robots.txt is in place and points crawlers to your sitemap.

Your XML sitemap is reachable at https://www.lavazzapro.co.uk/sitemap_index.xml.

Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

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

The site publishes https://www.lavazzapro.co.uk/llms.txt (3 KiB, 0 links), 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.

None of the pages we checked carries a noindex tag.

All 15 pages that loaded have a <title>.

The page declares a mobile viewport.

On a phone, the first screen shows a clear next step: “QUOTE”.

The homepage has 6 calls to action, for example “Quote”, “Contact Us” and “Get a quote”.

Analytics detected: Google Tag Manager.

Visitors can reach you directly: 1 phone link and 2 email links.

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