canopia.com website review

About 862 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.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.8 MB and 1.0 s of main-thread time.

13 images could be 423 KiB 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.

Your mobile performance score is 56 (desktop: 56). Pages that score under 90 lose visitors before the first paint.

About 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.

Google CDN costs a phone 297 ms of main-thread work and 741 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.

Google Tag Manager costs a phone 308 ms of main-thread work and 517 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.

A phone's processor spends 2.3 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

12 files are served with short cache lifetimes, so returning visitors download them again (236 KiB).

Polyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

12 long tasks block the main thread while loading, the longest for 138 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “1 / 5”.

The page becomes fully interactive after 17.9 s. Good is under 3.8 s.

Visually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 336 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.8 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.6 MB in 110 requests on a phone: scripts 2.0 MB (44), images 967 KiB (33) and other files 360 KiB (19). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example combined-front.webp at 450 px wide, shown at 136 px. Resized copies would save about 29 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 120.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 64 pages on canopia.com and 13 external pages.

There is no /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.

/support, /gallery, /tips-and-ideas, /certificates-standards and /privacy-policy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/product-category/accessories, /contact-us, /support, /gallery, /tips-and-ideas and /certificates-standards and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/contact-us and /support have no <h1> headline, so visitors and search engines get no clear main topic.

/product-category/greenhouses, /product-category/gazebos, /product-category/patio-covers, /product-category/door-awnings, /product-category/carports and /product-category/garden-rooms took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

canopia.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

canopia.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 8 fields (5 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,078 words of visible text.

DMARC is set to p=none, so mail pretending to be canopia.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 24 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.