petro-armor.com website review

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

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

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

Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (YouTube, Cloudflare CDN and Bootstrap CDN and others), adding 1.5 MB and 680 ms of main-thread time.

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

YouTube costs a phone 463 ms of main-thread work and 987 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.4 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

25 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

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

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

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.

Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.8 MB in 123 requests on a phone: scripts 1.2 MB (24), other files 723 KiB (77) and images 587 KiB (10). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Pump1.png at 1,380 px wide, shown at 120 px. Resized copies would save about 205 KiB.

1 image further down the page (87 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 0.80 g of CO₂e: 96.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 11 characters: “Petro Armor”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“”, “High Performance Renovation” and “Gas Island Renovation”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 28 pages on petro-armor.com and 11 external pages.

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.

Your homepage links to https://petro-armor.com/pages/solutions, which answers with an error. Visitors hit a dead end and search engines drop it.

https://petro-armor.com/collections/normal-kits, https://petro-armor.com/pages/gallery, https://petro-armor.com/pages/literature, https://petro-armor.com/pages/material-estimates, https://petro-armor.com/pages/application and https://petro-armor.com/pages/contractors and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://petro-armor.com/pages/literature has no <h1> headline, so visitors and search engines get no clear main topic.

https://petro-armor.com/pages/gallery, https://petro-armor.com/pages/literature, https://petro-armor.com/pages/material-estimates, https://petro-armor.com/pages/application, https://petro-armor.com/pages/contractors and https://petro-armor.com/pages/other-c-store-applications have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 10 pages linked from your homepage and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'fn')”.

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

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

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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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 10 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.