Website review, no card needed
bicycle-centre.com.au website review
Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 86 checks
This review found 32 issues worth fixing on bicycle-centre.com.au, 10 of them high impact, across 86 checks. The most urgent: reduce unused JavaScript. 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
87B- #8,513 of 124,112 reviewed websitesbeats 90%
- #4,874 of 69,786 online storesbeats 90%
- #4,721 of 63,466 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 113 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 123 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 118 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 120 ms |
| Sep 12, 2026 | 119 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 119 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 125 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 127 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.9 s · 608 KiBAbout 608 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.
Reduce unused CSS
1.7 s · 327 KiBAbout 327 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Maps, Shopify and storeify.app and others), adding 1.4 MB and 408 ms of main-thread time.
Improve image delivery
457 KiB15 images could be 457 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Maps adds 230 ms
230 msGoogle Maps costs a phone 230 ms of main-thread work and 405 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.
2,598 HTML elements
The page has 2,598 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 158 ms
158 msShopify costs a phone 158 ms of main-thread work and 969 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.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 654 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify JavaScript
150 ms · 18 KiB18 KiB could be saved by minifying JavaScript.
Render-blocking requests
100 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 70 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
8 KiB4 files are served with short cache lifetimes, so returning visitors download them again (8 KiB).
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.3 s
13.3 sYour largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bicycle Centre stores have the biggest range of new MTB's, …”.
Time to Interactive: 14.3 s
14.3 sThe page becomes fully interactive after 14.3 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 113 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 149 ms
149 msReal visitors wait 149 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 616 ms
616 msReal visitors wait 616 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 30 ms
30 msScripts block the page for only 30 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.1 MB in 212 requests
3.1 MBYour homepage downloads 3.1 MB in 212 requests on a phone: scripts 1.0 MB (65), other files 864 KiB (89) and images 779 KiB (21). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MERIDA-ecommuter-ehybrid.webp 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).
6 images in older formats
6 images (274 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.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
53 text elements with low contrast
53 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (12 elements)
Elements must only use permitted ARIA attributes: 12 elements on the page fail this check, rated serious by axe-core.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 74 images in the HTML carry an alt attribute.
51 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: 51 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (255 characters)
Your meta description is 255 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
327 internal links, 17 external
The homepage links to 327 pages on bicycle-centre.com.au and 17 external pages.
6 checks passed
Title: 63 characters
Your title is a healthy 63 characters: “E-Bikes, Road, Mountain & Kids Bikes | Bicycle Centre Australia”.
Canonical URL set
The canonical URL is https://bicycle-centre.com.au/.
Structured data in place
Structured data found: Organization 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 https://bicycle-centre.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: 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 (3,181 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bicycle-centre.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://bicycle-centre.com.au/a/store-locator/list has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 122 found) and read each the way a search engine does.
6 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 7 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
2 checks passed
Tap targets are thumb-sized
28 of 28 tappable elements near the top are at least 24 px.
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 2,305 words of copy
The homepage carries about 2,305 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop new season MTB, Road, eBikes & more” and “Shop Electric Bikes”.
20 calls to action
The homepage has 20 calls to action, for example “Shop bikes by brand”, “Shop all Bikes” and “Register your bike”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 191 testimonial or review blocks and 1 trust badge.
Opening hours shown
Your opening hours are on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
20 other companies contacted
Loading the homepage contacts 20 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 bicycle-centre.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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Forms · Storeify Store Locator
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
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on bicycle-centre.com.au, including 13 speed issues, 3 SEO issues and 4 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.