pennair.com website review

About 774 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google CDN, Google/Doubleclick Ads and Other Google APIs/SDKs and others), adding 1.1 MB and 519 ms of main-thread time.

21 images could be 307 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

Google CDN costs a phone 319 ms of main-thread work and 734 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.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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

Polyfills for old browsers add 18 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.

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.9 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 23.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WE HELP PEOPLE IN MANUFACTURING & CONSTRUCTION WITH PNEUMAT…”. Most of its time is element render delay (9.9 s).

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

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

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

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

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

Your homepage downloads 5.1 MB in 157 requests on a phone: scripts 2.0 MB (68), images 2.0 MB (39) and fonts 444 KiB (8). Under 2 MB keeps phones on slow connections fast.

15 images further down the page (483 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

8 images (311 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 1.44 g of CO₂e: 172.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

All page content should be contained by landmarks: 13 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 154 pages on pennair.com and 7 external pages.

There is no https://pennair.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://pennair.com/process-instrumentation, https://pennair.com/ul-certified-panel-shop and https://pennair.com/fluid-power-suppliers have no <h1> headline, so visitors and search engines get no clear main topic.

https://pennair.com/what-we-do, https://pennair.com/automation, https://pennair.com/what-we-do/automatic-lubrication, https://pennair.com/what-we-do/conveyor, https://pennair.com/what-we-do/electro-mechanical and https://pennair.com/what-we-do/hydraulics and 8 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

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

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and The Trade Desk (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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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