pierlite.com.au website review

27 images could be 7.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

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

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

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

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

39 KiB could be saved by minifying JavaScript.

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Unpkg and Cloudflare CDN and others), adding 502 KiB and 196 ms of main-thread time.

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.

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.

Your largest element takes 47.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WELCOME TO PIERLITE INSPIRED LED LIGHTING FOR COMMERCIAL, I…”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 12.9 MB in 148 requests on a phone: images 10.1 MB (47), scripts 1.7 MB (87) and stylesheets 968 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example shutterstock_721924594 (2).avif at 315 px wide, shown at 100 px. Resized copies would save about 5 KiB.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

Headings skip levels (h1 → h4 and h2 → h5), 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 20 characters: “Home Page - Pierlite”. 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 (“Welcome to Pierlite”, “Design Flexibility With new Kriss Linear” and “Trusted & Reliable Emergency Lighting”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 138 pages on pierlite.com.au and 1 external page.

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.

There is no https://pierlite.com.au/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://pierlite.com.au/socials/youtube has no <title>, so Google invents the link text in results.

https://pierlite.com.au/socials/youtube, https://pierlite.com.au/our-brands, https://pierlite.com.au/reference-projects, https://pierlite.com.au/warranty, https://pierlite.com.au/news and https://pierlite.com.au/contact-us and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pierlite.com.au/socials/youtube and https://pierlite.com.au/our-brands have no <h1> headline, so visitors and search engines get no clear main topic.

https://pierlite.com.au/products/indoor-led-lighting and https://pierlite.com.au/products/indoor-led-lighting/downlights took over 3 s to send their HTML from our server.

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

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

1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.css?t=_45201' violates the following Content Se…”.

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

Before a visitor clicks anything, the page loads Google Analytics 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 3 cookies (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.