polygongroup.com website review

hcaptcha.com costs a phone 1.8 s of main-thread work and 2.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

22 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).

3 third-party services load with your homepage (hcaptcha.com, Cookiebot and Monotype), adding 2.4 MB and 2.0 s of main-thread time.

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

About 470 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

The page has 2,047 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

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

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Solutions tailored to your industry”.

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

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

The layout shifts by 0.122 while loading, so content jumps under the reader's thumb. Good is under 0.1.

1 image have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 7.5 MB in 39 requests on a phone: media 4.2 MB (2), scripts 1.7 MB (9) and HTML 878 KiB (6). Under 2 MB keeps phones on slow connections fast.

3 images (118 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.

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

15 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

2 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

3 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate 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.

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

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

Your title is only 21 characters: “Start - Polygon Group”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No XML sitemap at https://www.polygongroup.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at polygongroup.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 128 pages on polygongroup.com and 2 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.polygongroup.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.

/, https://www.polygongroup.com/it-it, https://www.polygongroup.com/de-lu and https://www.polygongroup.com/nn-NO all use the title “Start - Polygon Group”. Search engines can't tell which page to show for a search, so each competes with the others.

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

3 images failed to load on a phone, for example https://www.polygongroup.com/.

23 of 96 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 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 647 words of visible text.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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