lightforce.co.nz website review

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 720 KiB 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.0 MB and 1.8 s of main-thread time.

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

About 954 KiB of JavaScript is downloaded but never used on this page.

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

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

Google CDN costs a phone 282 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.

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

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

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

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

10 KiB could be saved by minifying JavaScript.

7 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHAT'S YOUR SOLAR SAVINGS NUMBER? Checking out the benefits…”.

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

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

Real visitors wait 284 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

The layout shifts by 0.118 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-17, real Chrome visitors' tap response (inp) went from 180 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.2 MB in 207 requests on a phone: images 2.5 MB (34), scripts 2.5 MB (85) and fonts 432 KiB (7). Under 2 MB keeps phones on slow connections fast.

[email protected] is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (106 KiB) is 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.76 g of CO₂e: 210.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

2 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: 43 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.

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

There are 2 <h1> headlines (“New Zealand's Solar Experts” and “New Zealand's Solar Experts”). One clear main headline is easier for people and search engines.

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

The homepage links to 227 pages on lightforce.co.nz and 39 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 https://lightforce.co.nz/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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://lightforce.co.nz/solar-101, whose canonical is https://lightforce.co.nz/about-solar. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lightforce.co.nz/billbuster, https://lightforce.co.nz/solar-insights, https://lightforce.co.nz/solar-installer-locations and https://lightforce.co.nz/careers have no <h1> headline, so visitors and search engines get no clear main topic.

https://lightforce.co.nz/solar-installer-locations and https://lightforce.co.nz/product-guides took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=137015715&tm=gtm002&Ver=2&mid=60dfa651-431a-4944-a5b0-3db196b7d613&bo=1&sid=d51b3580cf2511f1bdc6b54346dd142c&vid=d51b6be0cf2511f18c0eed4209895184&vids=1&msclkid=N&pi=9.

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

3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://pixel.archipro.co.nz/ping?name=ap-pt-ping&id=lightforce-solar' from origin 'https://lightfo…”.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Your longest form asks for 22 fields (5 required). Every extra field lowers completion.

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

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 3,910 words of visible text.

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