Website review, no card needed
viridor.co.uk website review
Visit site (opens in a new tab)Reviewed 28 October 202630 issues · 75 checks
This review found 30 issues worth fixing on viridor.co.uk, 12 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
1.1 s · 17.9 MB20 files are served with short cache lifetimes, so returning visitors download them again (17.9 MB).
Reduce unused JavaScript
1.8 s · 631 KiBAbout 631 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Improve image delivery
600 ms · 17.6 MB15 images could be 17.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 79). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms19 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Vimeo adds 27 ms
27 msVimeo costs a phone 27 ms of main-thread work and 513 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Cookiebot and Vimeo and others), adding 894 KiB and 152 ms of main-thread time.
Document request latency
97 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.
Reduce unused CSS
40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 646 ms of it running JavaScript. That is comfortably low.
Server response: 296 ms
296 msYour server sent the HTML in 296 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.9 s
8.9 sThe first text or image appears after 8.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 10.3 s
10.3 sYour largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “As one of the UK’s leading innovators in resource recovery …”.
Time to Interactive: 15.0 s
15.0 sThe page becomes fully interactive after 15.0 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 74 ms
74 msScripts block the page for only 74 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 19.4 MB in 105 requests
19.4 MBYour homepage downloads 19.4 MB in 105 requests on a phone: images 17.8 MB (17), scripts 1.3 MB (45) and HTML 157 KiB (3). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 15.6 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
14.6 MB6 images are downloaded at several times the size a phone draws them, for example picture2.png at 4,400 px wide, shown at 390 px. Resized copies would save about 14.6 MB.
7 images in older formats
7 images (15.9 MB) are 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.
10 images below the first screen load straight away
10 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.5 g of CO₂ per visit
5.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.50 g of CO₂e: 660.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Headings should not be empty (5 elements)
Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (7 characters)
Your title is only 7 characters: “Viridor”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
40 internal links, 6 external
The homepage links to 40 pages on viridor.co.uk and 6 external pages.
3 checks passed
One H1 headline
Your main headline reads: “At Viridor, we are building a world where nothing goes to waste.”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://viridor.co.uk/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://viridor.co.uk/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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (877 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages share a title
/, https://viridor.co.uk/contact-us, https://viridor.co.uk/about-us, https://viridor.co.uk/energy-from-waste, https://viridor.co.uk/circular-solutions and https://viridor.co.uk/news-and-insights/viridor-keeps-the-equivalent-of-16-million-peoples-residential-waste-out-of-landfill and 4 others all use the title “Viridor”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://viridor.co.uk/contact-us, https://viridor.co.uk/about-us, https://viridor.co.uk/energy-from-waste, https://viridor.co.uk/circular-solutions, https://viridor.co.uk/news-and-insights/aimco-joins-equitix-led-investment-in-uk-energy-from-waste-leader-viridor and https://viridor.co.uk/news-and-insights/viridor-to-close-european-chemical-recycling-operations and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
20 of 20 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 931 words of copy
The homepage carries about 931 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”.
Social proof on the page
Social proof on the homepage: 22 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at viridor.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Tag Manager
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on viridor.co.uk, including 11 speed issues, 5 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.