Website review, no card needed
rachaelgrice.com website review
Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 73 checks
This review found 29 issues worth fixing on rachaelgrice.com, 7 of them high impact, across 73 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
70CClosest competitors among Squarespace websites
Compare side by sideOne 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.5 s · 496 KiBAbout 496 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.0 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
3 third-party services on the page
3 third-party services load with your homepage (Squarespace, Adobe TypeKit and squarespace-cdn.com), adding 1.5 MB and 564 ms of main-thread time.
Squarespace adds 561 ms
561 msSquarespace costs a phone 561 ms of main-thread work and 978 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 CSS
300 ms · 89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 330 ms. During a long task the page ignores taps.
Adobe TypeKit adds 3 ms
3 msAdobe TypeKit costs a phone 3 ms of main-thread work and 413 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.
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
90 KiB2 images could be 90 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 511 ms of it running JavaScript. That is comfortably low.
Server response: 52 ms
52 msYour server sent the HTML in 52 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 “unsplash-image-JZmyLsmpBOs.jpg”.
Time to Interactive: 9.5 s
9.5 sThe page becomes fully interactive after 9.5 s. Good is under 3.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 315 ms
315 msScripts block taps and scrolling for 315 ms in total while the page loads. Good is under 200 ms.
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.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 53.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 48 requests
1.6 MBYour homepage downloads 1.6 MB in 48 requests on a phone: scripts 916 KiB (24), fonts 439 KiB (13) and images 125 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (4 characters)
Your title is only 4 characters: “AURA”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 3 problems
Structured data found (LocalBusiness, Organization and WebSite) but with 3 problems, for example “Organization: missing name”.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
12 internal links, 1 external
The homepage links to 12 pages on rachaelgrice.com and 1 external page.
4 checks passed
One H1 headline
Your main headline reads: “AURA”.
Canonical URL set
The canonical URL is http://www.rachaelgrice.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://www.rachaelgrice.com/sitemap.xml.
AI search readiness
Organization data is thin (1 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.rachaelgrice.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 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.
Other pages
6 pages without a meta description
https://www.rachaelgrice.com/about, https://www.rachaelgrice.com/contact, https://www.rachaelgrice.com/bookmyspot, https://www.rachaelgrice.com/breathewrite, https://www.rachaelgrice.com/space-focusing and https://www.rachaelgrice.com/extras have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages with very little text
https://www.rachaelgrice.com/contact, https://www.rachaelgrice.com/bookmyspot, https://www.rachaelgrice.com/space-focusing and https://www.rachaelgrice.com/extras 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.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 6 pages we checked loaded without an error.
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 6 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/sitecss/52019bf7e4b090cd25bf097b/101/4fd11f32c4aad9…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 21 words
The homepage has only about 21 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT” and “BOOK MY SPOT”.
4 calls to action
The homepage has 4 calls to action, for example “contact” and “book my spot”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 rachaelgrice.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Squarespace
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on rachaelgrice.com, including 13 speed issues, 5 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.