polymerhq.io website review

About 1.0 MB 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.

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

About 255 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Hubspot and hsappstatic.net and others), adding 2.2 MB and 1.2 s of main-thread time.

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

12 images could be 761 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

hsappstatic.net costs a phone 256 ms of main-thread work and 881 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.

Hubspot costs a phone 292 ms of main-thread work and 333 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 3.2 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying CSS.

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

For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.

Real visitors see the first content after 4.4 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.

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

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Secure AI workflows at runtime”.

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

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

Your homepage downloads 4.6 MB in 163 requests on a phone: scripts 2.2 MB (64), images 1.2 MB (36) and fonts 752 KiB (16). Under 2 MB keeps phones on slow connections fast.

6 images (707 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 further down the page (118 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

3 visible links have no text or label, so screen readers cannot say where they go.

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

10 links have no real href, so search engines can't follow them.

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

The homepage links to 89 pages on polymerhq.io and 22 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description 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 /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.

/pricing and /solutions have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://www.polymerhq.io/.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “$ is not a function”.

Chrome logged issues while loading the page (“Cookie”).

1 link to other sites is dead, for example https://www.erkareyapi.com/ (503).

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.

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.

polymerhq.io 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.

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.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

DMARC is set to p=none, so mail pretending to be polymerhq.io 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, HubSpot and LinkedIn Insight (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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