Website review, no card needed

solarworldpower.com.au logo

solarworldpower.com.au website review

Visit site (opens in a new tab)Reviewed 19 October 202639 issues · 92 checks

This review found 39 issues worth fixing on solarworldpower.com.au, 12 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.1 s1.5 sMay 2Oct 173.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.3 s
May 16, 20263.4 s
May 23, 20263.7 s
May 30, 20263.6 s
Jun 6, 20263.8 s
Jun 13, 20263.5 s
Jun 20, 20263.3 s
Jun 27, 20263.1 s
Jul 4, 20262.9 s
Jul 11, 20261.8 s
Jul 18, 20262.2 s
Jul 25, 20262.8 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20262.9 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20263.2 s
Oct 10, 20263.3 s
Oct 17, 20263.5 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of solarworldpower.com.au (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. solarworldpower.com.au at 1.0 s1.0 s
  2. solarworldpower.com.au at 2.0 s2.0 s
  3. solarworldpower.com.au at 2.9 s2.9 s
  4. solarworldpower.com.au at 3.9 s3.9 s
  5. solarworldpower.com.au at 4.9 s4.9 s
  6. solarworldpower.com.au at 5.9 s5.9 s
  7. solarworldpower.com.au at 6.9 s6.9 s
  8. solarworldpower.com.au at 7.8 s7.8 s

Speed

12 to fix55
  • Use efficient cache lifetimes

    1.6 s · 466 KiB

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

  • Render-blocking requests

    1.8 s

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

  • Font display

    1.6 s

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

  • Mobile performance score: 55

    55/100

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

  • Improve image delivery

    600 ms · 227 KiB

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

  • Reduce unused CSS

    600 ms · 115 KiB

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

  • Reduce unused JavaScript

    450 ms · 153 KiB

    About 153 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Document request latency

    600 ms

    The HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    581 ms

    Reduce initial server response time. Google estimates savings of 581 ms on a phone.

  • 2,404 HTML elements

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

  • Main-thread work: 2.3 s

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

  • Server response: 681 ms

    681 ms

    Your server takes 681 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, trustindex.io and Cloudflare and others), adding 312 KiB and 187 ms of main-thread time.

  • Minify CSS

    150 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    24 KiB

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

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

Core Web Vitals

9 to fix50
  • Fails Core Web Vitals for real visitors

    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-user FCP: 3.2 s

    3.2 s

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

  • First Contentful Paint: 9.1 s

    9.1 s

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

  • Largest Contentful Paint: 15.7 s

    15.7 s

    Your largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cut Your Power Bills with Smart Solar & Battery Solutions S…”.

  • Speed Index: 14.5 s

    14.5 s

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

  • Time to Interactive: 16.9 s

    16.9 s

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

  • Real-user LCP: 3.5 s

    3.5 s

    Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 21 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

3 checks passed
  • Real-user CLS: 0.05

    0.05

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

  • Cumulative Layout Shift: 0.045

    0.045

    The layout barely moves while loading (CLS 0.045, good is under 0.1).

  • Total Blocking Time: 4 ms

    4 ms

    Scripts block the page for only 4 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 2.1 MB in 367 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 367 requests on a phone: images 882 KiB (36), scripts 618 KiB (44) and fonts 296 KiB (223). Under 2 MB keeps phones on slow connections fast.

  • 11 images below the first screen load straight away

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

  • 1 image far larger than shown

    76 KiB

    1 image is downloaded at several times the size a phone draws it, for example netcc-logo-approved-seller-full_rgb.png at 969 px wide, shown at 71 px. Resized copies would save about 76 KiB.

  • 9 images in older formats

    9 images (392 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.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

Accessibility

9 to fixGoogle 9091
  • 5 tap targets too small

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

  • 4 text elements with low contrast

    4 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 (99 elements)

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

  • No main landmark

    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)

    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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • The skip-link target should exist and be focusable (1 element)

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

  • 36 form fields without a label

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

  • Headings should not be empty (1 element)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 92 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9288
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 8 links with vague text

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

  • 236 internal links, 8 external

    The homepage links to 236 pages on solarworldpower.com.au and 8 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Get top-quality solar installation in Sydney! Trusted for 15+ years, we offer solar solutions for homes & businesses. G…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Solar World - Residential and Commercial Solar panel Installer”.

  • Canonical URL set

    The canonical URL is https://solarworldpower.com.au/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://solarworldpower.com.au/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://solarworldpower.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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,477 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 12 pages slow to respond

    https://solarworldpower.com.au/13-2kw-solar-system-price-nsw, https://solarworldpower.com.au/15kw-solar-system, https://solarworldpower.com.au/30kw-solar-system-price, https://solarworldpower.com.au/ground-mounted-solar, https://solarworldpower.com.au/fox-ess-battery-review and https://solarworldpower.com.au/foxess-eq-battery-price-sydney and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7393
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://solarworldpower.com.au/' was loaded over HTTPS, but requested an insecure font 'htt…”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    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.

  • A 8-field form

    Your longest form asks for 8 fields (4 required). Every extra field lowers completion.

  • No opening hours

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

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,712 words of copy

    The homepage carries about 1,712 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get A Free Quote”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Get A Free Quote”, “Get a Free Quote” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 38 testimonial or review blocks, 1 customer or partner logo and 43 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 6 cookies set on arrival

    6

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

  • No consent tool detected

    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.

  • 9 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at solarworldpower.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on solarworldpower.com.au, including 21 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25