Website review, no card needed
star-naming.com.au website review
Visit site (opens in a new tab)Reviewed 11 November 202622 issues · 78 checks
This review found 22 issues worth fixing on star-naming.com.au, 6 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
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
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 574 KiB13 images could be 574 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
700 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Reduce unused CSS
270 ms · 25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 270 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 74 KiB2 files are served with short cache lifetimes, so returning visitors download them again (74 KiB).
Reduce unused JavaScript
150 ms · 25 KiBAbout 25 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.
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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
7 third-party services on the page
7 third-party services load with your homepage (Google Fonts, Shopify and gorgias.chat and others), adding 303 KiB and 0 ms of main-thread time.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 151 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 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: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “For Christmas: choose Express shipping for your printed gif…”.
Cumulative Layout Shift: 0.293
0.293The layout shifts by 0.293 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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.
Time to Interactive: 5.3 s
5.3 sThe page becomes fully interactive after 5.3 s. Good is under 3.8 s.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 195 ms
195 msReal visitors wait 195 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 651 ms
651 msReal visitors wait 651 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 59% faster for real visitors
-59%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 512 ms to 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Speed Index: 1.7 s
1.7 sVisually, the page fills in at 1.7 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 37 ms
37 msScripts block the page for only 37 ms while loading. Good is under 200 ms.
Images and page weight
8 images below the first screen load straight away
8 images further down the page (270 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.4 MB in 39 requests
1.4 MBYour homepage downloads 1.4 MB in 39 requests on a phone: images 853 KiB (16), scripts 301 KiB (10) and HTML 149 KiB (1). That is a lean page.
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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 51 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
35 internal links, 6 external
The homepage links to 35 pages on star-naming.com.au and 6 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Name a star for someone special – registered in the International Space Registry, with certificate & free AR app to fin…”.
One H1 headline
Your main headline reads: “Name a Star and outshine ordinary gifts”.
Title: 50 characters
Your title is a healthy 50 characters: “Name a Star – Certificate & Star Map | Star-Naming”.
Canonical URL set
The canonical URL is https://star-naming.com/.
Structured data in place
Structured data found: FAQPage.
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://star-naming.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (2,631 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://star-naming.com/llms.txt (4 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://star-naming.com/pages/name-a-star-pricing is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share a title
https://star-naming.com/pages/star-configurator/silvernova, https://star-naming.com/pages/star-configurator/supernova, https://star-naming.com/pages/star-configurator/duonova and https://star-naming.com/pages/star-configurator/special-gift-box all use the title “Star Configurator”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://star-naming.com/pages/star-configurator/silvernova, https://star-naming.com/pages/star-configurator/supernova, https://star-naming.com/pages/star-configurator/duonova and https://star-naming.com/pages/star-configurator/special-gift-box have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages without an H1
https://star-naming.com/pages/star-configurator/silvernova, https://star-naming.com/pages/star-configurator/supernova, https://star-naming.com/pages/star-configurator/duonova, https://star-naming.com/pages/star-configurator/special-gift-box, https://star-naming.com/pages/name-a-star-faq and https://star-naming.com/pages/reviews have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://star-naming.com/pages/star-configurator/silvernova, https://star-naming.com/pages/star-configurator/supernova, https://star-naming.com/pages/star-configurator/duonova and https://star-naming.com/pages/star-configurator/special-gift-box 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 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 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,038 words of copy
The homepage carries about 2,038 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Name a Star — Pricing & Gift Sets”, “Buy a Star” and “Buy a Star from NASA?”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks, 3 customer or partner logos, a star rating, 26 trust badges and “1,800+ reviews”.
Analytics in place
Analytics detected: Google Analytics, Microsoft Clarity and TikTok Pixel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
8 other companies contacted
Loading the homepage contacts 8 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 star-naming.com.au, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on star-naming.com.au, including 8 speed 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.