Website review, no card needed
bluettipower.com.au website review
Visit site (opens in a new tab)Reviewed 5 November 202650 issues · 99 checks
This review found 50 issues worth fixing on bluettipower.com.au, 16 of them high impact, across 99 checks. The most urgent: main-thread work: 26.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69D- #108,208 of 126,357 reviewed websitesbeats 12%
- #64,577 of 70,445 online storesbeats 7%
- #59,460 of 63,948 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 214 ms |
| May 23, 2026 | 229 ms |
| May 30, 2026 | 237 ms |
| Jun 6, 2026 | 246 ms |
| Jun 13, 2026 | 239 ms |
| Jun 20, 2026 | 244 ms |
| Jun 27, 2026 | 245 ms |
| Jul 4, 2026 | 244 ms |
| Jul 11, 2026 | 237 ms |
| Jul 18, 2026 | 229 ms |
| Jul 25, 2026 | 222 ms |
| Aug 1, 2026 | 212 ms |
| Aug 8, 2026 | 209 ms |
| Aug 15, 2026 | 211 ms |
| Aug 22, 2026 | 212 ms |
| Aug 29, 2026 | 217 ms |
| Sep 5, 2026 | 221 ms |
| Sep 12, 2026 | 214 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 208 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 214 ms |
| Oct 24, 2026 | 216 ms |
| Oct 31, 2026 | 223 ms |
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
How it loaded on a phone
1.3 s
2.6 s
4.0 s
5.3 s
6.6 s
7.9 s
9.2 s
10.6 s
Speed
Main-thread work: 26.5 s
A phone's processor spends 26.5 s on main-thread work while loading, 11.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.6 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,208 HTML elements
The page has 5,208 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and run.app and others), adding 2.0 MB and 3.0 s of main-thread time.
Reduce unused JavaScript
450 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.
Use efficient cache lifetimes
700 ms · 973 KiB41 files are served with short cache lifetimes, so returning visitors download them again (973 KiB).
Improve image delivery
650 ms · 436 KiB5 images could be 436 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Reduce unused CSS
750 ms · 126 KiBAbout 126 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.
Google Tag Manager adds 676 ms
676 msGoogle Tag Manager costs a phone 676 ms of main-thread work and 325 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.
Facebook adds 606 ms
606 msFacebook costs a phone 606 ms of main-thread work and 283 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.
Accessibe Accessibility Overlay adds 377 ms
377 msAccessibe Accessibility Overlay costs a phone 377 ms of main-thread work and 249 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.
run.app adds 379 ms
379 msrun.app costs a phone 379 ms of main-thread work and 192 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.
Klaviyo adds 334 ms
334 msKlaviyo costs a phone 334 ms of main-thread work and 324 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.
Minify CSS
150 ms · 6 KiB6 KiB could be saved by minifying CSS.
Legacy JavaScript
80 KiBPolyfills for old browsers add 80 KiB JavaScript that modern phones do not need.
Minify JavaScript
8 KiB8 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.
1 checks passed
Server response: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 9.5 s
9.5 sYour largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 5.4 s
5.4 sScripts block taps and scrolling for 5.4 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 40.8 s
40.8 sThe page becomes fully interactive after 40.8 s. Good is under 3.8 s.
Speed Index: 14.5 s
14.5 sVisually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Real-user INP: 239 ms
239 msReal visitors wait 239 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 214 ms to 223 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 439 requests
7.6 MBYour homepage downloads 7.6 MB in 439 requests on a phone: scripts 4.1 MB (200), images 1.4 MB (37) and other files 1.3 MB (169). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
PV1002_1f8bd4e1-1311-4c11-a29b-29c902ba3651.webp weighs 2.1 MB. On a phone connection a single image that size takes seconds.
2 images far larger than shown
2.1 MB2 images are downloaded at several times the size a phone draws them, for example PV1002_1f8bd4e1-1311-4c11-a29b-29c902ba3651.webp at 2,000 px wide, shown at 56 px. Resized copies would save about 2.1 MB.
5 images in older formats
5 images (2.3 MB) 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 2.2 g of CO₂ per visit
2.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.16 g of CO₂e: 259.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
29 text elements with low contrast
29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
20 images without alt text
20 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (162 characters)
Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//checkout.bluettipower.com.au/cdn/shop/files/BLUETTI_L…”.
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.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
188 internal links, 69 external
The homepage links to 188 pages on bluettipower.com.au and 69 external pages.
6 checks passed
One H1 headline
Your main headline reads: “solar generator portable power station”.
Title: 63 characters
Your title is a healthy 63 characters: “Portable Power Station, Solar Generator, Home Battery | BLUETTI”.
Canonical URL set
The canonical URL is https://www.bluettipower.com.au/.
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 https://www.bluettipower.com.au/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,641 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bluettipower.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.bluettipower.com.au/products/bluetti-ep2000-2-b700-home-energy and https://www.bluettipower.com.au/pages/ep2000 all use the title “BLUETTI AU”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.bluettipower.com.au/products/bluetti-ep2000-2-b700-home-energy, https://www.bluettipower.com.au/pages/ep2000 and https://www.bluettipower.com.au/products/bluetti-elite-200-v2-220w-solar-generator-kit have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.bluettipower.com.au/products/bluetti-elite-400-portable-power-station and https://www.bluettipower.com.au/products/elite-400-portable-power-station-500w use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.bluettipower.com.au/products/bluetti-elite-400-portable-power-station, whose canonical is https://www.bluettipower.com.au/products/elite-400-portable-power-station. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.bluettipower.com.au/pages/black-friday and https://www.bluettipower.com.au/pages/streams/2d3a04b1-6ee1-11f1-a916-3f9c30163b89 have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.bluettipower.com.au/pages/black-friday and https://www.bluettipower.com.au/pages/streams/2d3a04b1-6ee1-11f1-a916-3f9c30163b89 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.
8 pages slow to respond
https://www.bluettipower.com.au/products/fridgepower-battery-backup, https://www.bluettipower.com.au/products/bluetti-elite-400-portable-power-station, https://www.bluettipower.com.au/pages/ep760, https://www.bluettipower.com.au/products/bluetti-ep2000-2-b700-home-energy, https://www.bluettipower.com.au/products/elite-100-v2-portable-power-station and https://www.bluettipower.com.au/products/elite-200-v2-portable-power-station and 2 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 67 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
40 small tap targets
40 of 84 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “取消之前的 getLadderGiftStatus 请求”.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 1,075 words of copy
The homepage carries about 1,075 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Buy Now” and “Shop Now”.
66 calls to action
The homepage has 66 calls to action, for example “Register”, “Buy Now” and “Shop Now”.
4 short forms
4 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads and 1 more (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
49 other companies contacted
Loading the homepage contacts 49 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 bluettipower.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Gocertify · Judge Me Reviews · Klaviyo Email Marketing Sms · Pushowl · Version · goaffpro.com · webgains.com · verifypass.com · cfjump.com · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on bluettipower.com.au, including 24 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.