Website review, no card needed
anesco.com website review
Visit site (opens in a new tab)Reviewed 20 November 202638 issues · 89 checks
This review found 38 issues worth fixing on anesco.com, 13 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.6 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.8 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 135 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 126 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 116 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 140 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 110 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 88 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 129 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 158 ms |
| Nov 7, 2026 | 157 ms |
| Nov 14, 2026 | 138 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
Speed
Reduce unused JavaScript
3.9 s · 391 KiBAbout 391 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Render-blocking requests
1.7 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 152 KiBAbout 152 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Improve image delivery
412 KiB3 images could be 412 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 268 ms
268 msGoogle CDN costs a phone 268 ms of main-thread work and 742 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 CDN, Other Google APIs/SDKs and Adobe TypeKit and others), adding 914 KiB and 296 ms of main-thread time.
Legacy JavaScript
150 ms · 16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 78 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 994 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user CLS: 0.52
0.52For real visitors the layout shifts by 0.52 (75th percentile). Good is under 0.1.
First Contentful Paint: 8.6 s
8.6 sThe first text or image appears after 8.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 16.2 s
16.2 sYour largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Enabling the transition to a low carbon economy”.
Time to Interactive: 16.5 s
16.5 sThe page becomes fully interactive after 16.5 s. Good is under 3.8 s.
Speed Index: 8.6 s
8.6 sVisually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 107 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 909 ms
909 msReal visitors wait 909 ms for your server to start answering (75th percentile). Good is under 800 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 135 ms
135 msReal visitors wait 135 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.086
0.086The layout barely moves while loading (CLS 0.086, good is under 0.1).
Total Blocking Time: 29 ms
29 msScripts block the page for only 29 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.0 MB in 83 requests
12.0 MBYour homepage downloads 12.0 MB in 83 requests on a phone: media 6.2 MB (3), images 4.0 MB (17) and scripts 1,012 KiB (30). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
6 images in older formats
6 images (2.6 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.
About 3.4 g of CO₂ per visit
3.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.41 g of CO₂e: 409.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 17 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
53 internal links, 19 external
The homepage links to 53 pages on anesco.com and 19 external pages.
8 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “At Anesco we develop, design, construct, operate and maintain high performing renewable energy projects, as well as....…”.
One H1 headline
Your main headline reads: “Enabling the transition to a low carbon economy”.
Title: 57 characters
Your title is a healthy 57 characters: “Home Page - Anesco renewable energy and energy efficiency”.
Canonical URL set
The canonical URL is https://anesco.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage 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.
XML sitemap found
Your XML sitemap is reachable at https://anesco.com/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://anesco.com/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 (3,871 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a meta description
https://anesco.com/nl, https://anesco.com/be, https://anesco.com/be-fr and https://anesco.com/dk use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 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
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
5 small tap targets
5 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 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
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.
A 9-field form
Your longest form asks for 9 fields (0 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 1,020 words of copy
The homepage carries about 1,020 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 5 trust badges.
Analytics in place
Analytics detected: Matomo.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 anesco.com, 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
- Analytics
- Matomo
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on anesco.com, including 17 speed issues, 2 SEO issues and 3 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.