Free site check

Case 4 · Residential and commercial solar and battery · Australia

A solar installer in Australia

A four-office Australian solar and battery installer, in business since 2014, doing residential and commercial rooftop PV plus storage.

a solar installer, Australia
The solarprojects website as built, at desktop width. The same site at phone width.

In a remarkably short time, bewsti gave our solar company a logo, a complete brand book and a clean, modern website.

What impressed us most was how quickly they understood our industry and turned our vision into a strong, professional identity. The quality was excellent at every stage, from the first concepts to the final files.

Communication was clear throughout, and the results exceeded our expectations. We now have a brand that truly represents us and a website we’re proud to share.

We highly recommend bewsti to any company that wants high-quality branding and web design, delivered efficiently and professionally.

The team at the solar installer

At a glance

4.1 KB

The styling file every page waits for went from 146 KB to 4.1 KB.

146 KB to 4.1 KB.

2.3 s

The main content appears in 2.3 seconds, down from 5.0.

The largest element, 5.0 s to 2.3 s.

22.0 s

A person finished the inquiry form in 22.0 seconds, keyboard only.

22.0 s on desktop, 21.9 s on a phone.

What the business does

A four-office Australian solar and battery installer, in business since 2014, doing residential and commercial rooftop PV plus storage, with the commercial side, 80 kW to 200 kW rooftops and embedded networks, as the priority book of business. The existing site was a 2019 build that measured badly on every axis.

What was wrong when we started
  • A 146 KB render-blocking stylesheet on every page.
  • The homepage HTML was 240 KB raw, 40.3 KB gzipped, because a decorative field was drawn as 5,489 SVG circle elements in the markup.
  • A lab speed score of 74 out of 100. The largest element took 5.0 seconds to appear.
  • Total blocking time 350 ms.
The numbers

The form was timed by a person typing it, keyboard only, at about forty words a minute with a pause to read each label, because a form that takes under a minute is a form somebody finishes. It came out at 22.0 seconds.

146 KB to 4.1 KB

The render-blocking stylesheet on every page.

127 KB to 41 KB

The shared CSS bundle across the site.

74 to 90, and LCP 5.0 s to 2.3 s

Lab speed score and the time for the largest element to appear, on the first measured build.

5,489 to 14

SVG circle elements in the homepage HTML.

240 KB to 67.7 KB raw, 40.3 KB to 14.4 KB gzipped

Homepage HTML weight.

350 ms to 90-190 ms

Total blocking time.

0.97 KB raw, 0.47 KB gzipped

The drawn offices map, from public-domain geodata, as one inlined SVG path.

99 / 100 / 100, CLS 0, TBT 0 ms

Lab scores on a phone profile, on the built output: speed, accessibility, best practices.

680 to 800 ms, CLS 0 on all five

Largest contentful paint across five pages at 390x844 under applied 4x CPU throttle and slow 4G.

0 of 1,060

Broken internal links across 44 files.

22.0 s desktop, 21.9 s on a 390px phone

A real person completing the inquiry form, keyboard only, at 300 ms per character with a 1.2 s pause to read each label.

What we decided

The decorative field moved out of the HTML.

Why

5,489 Circle elements became 14. The homepage HTML went from 240 KB to 67.7 KB raw and 40.3 KB to 14.4 KB gzipped, and total blocking time went from 350 ms to between 90 and 190 ms.

The offices map is drawn, not embedded.

Why

One inlined SVG path from public-domain map data: 0.97 KB raw, 0.47 KB gzipped, zero extra requests, no API key and no account. A real embed needs a cloud account with billing attached and is one of the heaviest things that can go on a page.

Rejected: a live interactive map, which would have been the heaviest thing on every page it touched.

What they own now

  • The repository, the built site and the deploy workflow
  • A launch guide: every detail to confirm and every switch to flip on the day

Yours, next.

See how your home page reads to a customer.

The reply opens at once. No call, no email.