Website review, no card needed
alitex.co.uk website review
Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 90 checks
This review found 34 issues worth fixing on alitex.co.uk, 12 of them high impact, across 90 checks. The most urgent: mobile performance score: 35. 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
79C- #56,263 of 126,333 reviewed websitesbeats 50%
- #36,691 of 70,435 online storesbeats 42%
- #827 of 2,970 WooCommerce storesbeats 68%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.6 s |
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 103 ms |
| May 2, 2026 | 102 ms |
| May 9, 2026 | 97 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 100 ms |
| May 30, 2026 | 102 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 107 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 108 ms |
| Aug 1, 2026 | 108 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 118 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 130 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.9 s
3.6 s
4.3 s
5.0 s
5.7 s
Speed
Mobile performance score: 35
35/100Your mobile performance score is 35 (desktop: 80). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google CDN and others), adding 1.7 MB and 2.1 s of main-thread time.
Improve image delivery
1.2 MB6 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 749 ms
749 msGoogle Tag Manager costs a phone 749 ms of main-thread work and 683 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.
Reduce unused JavaScript
775 KiBAbout 775 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
450 ms · 197 KiBAbout 197 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
FontAwesome CDN adds 581 ms
581 msFontAwesome CDN costs a phone 581 ms of main-thread work and 292 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.
Render-blocking requests
500 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Use efficient cache lifetimes
150 ms · 311 KiB18 files are served with short cache lifetimes, so returning visitors download them again (311 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.
2,002 HTML elements
The page has 2,002 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 155 ms
155 msGoogle CDN costs a phone 155 ms of main-thread work and 347 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.
Legacy JavaScript
150 ms · 41 KiBPolyfills for old browsers add 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
50 KiB50 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 80 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 96 ms
96 msYour server sent the HTML in 96 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 103 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
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-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 134 ms
134 msReal visitors wait 134 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 661 ms
661 msReal visitors wait 661 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Images and page weight
Page weight: 4.4 MB in 182 requests
4.4 MBYour homepage downloads 4.4 MB in 182 requests on a phone: images 1.9 MB (40), scripts 1.8 MB (66) and fonts 339 KiB (12). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (362 KiB) 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.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.24 g of CO₂e: 148.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
48 text elements with low contrast
48 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
196 internal links, 23 external
The homepage links to 196 pages on alitex.co.uk and 23 external pages.
8 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “We're passionate about all that grows. our modern Victorian greenhouses are perfect for the growth of plants, fruit & v…”.
One H1 headline
Your main headline reads: “Passionate about all that grows”.
Title: 33 characters
Your title is a healthy 33 characters: “Victorian Greenhouses | Alitex UK”.
Canonical URL set
The canonical URL is https://www.alitex.co.uk/.
Structured data in place
Structured data found: AboutPage, ImageObject, Organization, Place and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://www.alitex.co.uk/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.alitex.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 (1,584 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
7 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 a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97151400&Ver=2&mid=df66af20-65d0-46ce-81b0-4e87893cb215&bo=1&sid=c4e41950cb5a11f1ae6e85fd1010ffc1&vid=c4e43c20cb5a11f1990a0dbdb015f646&vids=1&msclkid=N&pi=918639831&lg.
10 small tap targets
10 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
A 9-field form
Your longest form asks for 9 fields (6 required). Every extra field lowers completion.
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 1,577 words of copy
The homepage carries about 1,577 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request A Brochure” and “Book a Visit”.
36 calls to action
The homepage has 36 calls to action, for example “Accessory Shop”, “Contact us” and “Request A Brochure”.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, 1 customer or partner logo and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity, Hotjar and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
43 other companies contacted
Loading the homepage contacts 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 alitex.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
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager | Hotjar | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on alitex.co.uk, including 20 speed issues, 1 SEO issue and 2 conversion gaps. 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.