Website review, no card needed
princesshighway.co.nz website review
Visit site (opens in a new tab)Reviewed 6 November 202639 issues · 89 checks
This review found 39 issues worth fixing on princesshighway.co.nz, 11 of them high impact, across 89 checks. The most urgent: main-thread work: 6.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
80B- #49,178 of 126,652 reviewed websitesbeats 55%
- #32,212 of 70,540 online storesbeats 48%
- #30,924 of 64,024 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 162 ms |
| May 23, 2026 | 166 ms |
| May 30, 2026 | 170 ms |
| Jun 6, 2026 | 174 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 182 ms |
| Jul 4, 2026 | 183 ms |
| Jul 11, 2026 | 183 ms |
| Jul 18, 2026 | 182 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 180 ms |
| Aug 22, 2026 | 181 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 192 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 193 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 201 ms |
| Oct 31, 2026 | 200 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.1 s
2.2 s
3.3 s
4.4 s
5.4 s
6.5 s
7.6 s
8.7 s
Speed
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,113 HTML elements
The page has 6,113 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms18 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 1.1 MB and 645 ms of main-thread time.
Improve image delivery
572 KiB13 images could be 572 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Klaviyo adds 238 ms
238 msKlaviyo costs a phone 238 ms of main-thread work and 315 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.
Shopify adds 176 ms
176 msShopify costs a phone 176 ms of main-thread work and 735 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.
Reduce unused JavaScript
150 ms · 94 KiBAbout 94 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 211 ms. During a long task the page ignores taps.
Legacy JavaScript
63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
55 KiB13 files are served with short cache lifetimes, so returning visitors download them again (55 KiB).
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Largest Contentful Paint: 4.6 s
4.6 sYour largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 0.313
0.313The layout shifts by 0.313 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 162 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 448 ms
448 msScripts block taps and scrolling for 448 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 541 ms
541 msReal visitors wait 541 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.8 MB in 516 requests
3.8 MBYour homepage downloads 3.8 MB in 516 requests on a phone: images 1.3 MB (38), scripts 1.2 MB (234) and other files 1.0 MB (187). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
04_Mob_2060OffDresses.jpg 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).
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Required ARIA attributes must be provided (15 elements)
Required ARIA attributes must be provided: 15 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
29 links without text
29 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.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “Princess Highway”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
28 links crawlers can't follow
28 links have no real href, so search engines can't follow them.
447 internal links, 10 external
The homepage links to 447 pages on princesshighway.co.nz and 10 external pages.
6 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Discover the Australian label Princess Highway, which brings vintage-inspired charm, timeless prints, and flattering fi…”.
Canonical URL set
The canonical URL is https://princesshighway.com.au/en-us.
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://princesshighway.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 (2,217 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://princesshighway.com.au/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://princesshighway.com.au/en-us/collections/all and https://princesshighway.com.au/en-us/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://princesshighway.com.au/en-us/collections/dresses-jumpsuits and https://princesshighway.com.au/en-us/collections/sale-tops-blouses have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 138 found) and read each the way a search engine does.
5 checks passed
Linked pages load
8 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 8 pages that loaded have a <title>.
Best practices
14 small tap targets
14 of 54 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'parentNode')”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 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 327 words of copy
The homepage carries about 327 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
35 calls to action
The homepage has 35 calls to action, for example “SHOP SALE”, “shop sale clothing” and “shop by sale price”.
7 short forms
7 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
31 other companies contacted
Loading the homepage contacts 31 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 princesshighway.co.nz, 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
Instafeed · Microsoft Clarity · Factoryx App · Klaviyo Email Marketing Sms · Oxi Social Login Wishlist · Countdown Timer · Spin Wheel · Ultimate Searh · cfjump.com · merchantyard.com
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
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
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 princesshighway.co.nz, including 16 speed issues, 3 SEO issues and 5 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.