Website review, no card needed
writualplanner.com website review
Visit site (opens in a new tab)Reviewed 9 November 202619 issues · 73 checks
This review found 19 issues worth fixing on writualplanner.com, 2 of them high impact, across 73 checks. The most urgent: no social proof. 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
91A- #1,137 of 88,980 reviewed websitesbeats 98%
- #479 of 46,344 online storesbeats 98%
- #455 of 41,598 Shopify storesbeats 98%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 940 ms |
| Jul 4, 2026 | 789 ms |
| Jul 11, 2026 | 760 ms |
| Jul 18, 2026 | 751 ms |
| Jul 25, 2026 | 730 ms |
| Aug 1, 2026 | 726 ms |
| Aug 8, 2026 | 742 ms |
| Aug 15, 2026 | 726 ms |
| Aug 22, 2026 | 748 ms |
| Aug 29, 2026 | 769 ms |
| Sep 5, 2026 | 814 ms |
| Sep 12, 2026 | 836 ms |
| Sep 19, 2026 | 872 ms |
| Sep 26, 2026 | 891 ms |
| Oct 3, 2026 | 881 ms |
| Oct 10, 2026 | 865 ms |
| Oct 17, 2026 | 804 ms |
| Oct 24, 2026 | 745 ms |
| Oct 31, 2026 | 732 ms |
| Nov 7, 2026 | 729 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 104 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 116 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 110 ms |
| Nov 7, 2026 | 109 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
Improve image delivery
845 KiB25 images could be 845 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
750 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.
1,713 HTML elements
The page has 1,713 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
85 KiB11 files are served with short cache lifetimes, so returning visitors download them again (85 KiB).
Reduce unused CSS
59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page.
8 third-party services on the page
8 third-party services load with your homepage (shgcdn3.com, Shopify and cloudfront.net and others), adding 125 KiB and 33 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.
3 checks passed
Mobile performance score: 100
100/100Your mobile performance score is 100. That is in Google's “good” band (90 and up).
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 75 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 104 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
13 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 100 ms
100 msReal visitors wait 100 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 388 ms
388 msReal visitors wait 388 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Largest Contentful Paint: 1.1 s
1.1 sYour largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold.
Speed Index: 1.4 s
1.4 sVisually, the page fills in at 1.4 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.1 s
1.1 sThe page is fully interactive after 1.1 s.
Images and page weight
Page weight: 2.9 MB in 68 requests
2.9 MBYour homepage downloads 2.9 MB in 68 requests on a phone: images 2.4 MB (36), scripts 316 KiB (28) and stylesheets 71 KiB (2). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
2_d8f6f3e2-c839-4a15-9ff7-7ff584623588.png 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).
4 images far larger than shown
166 KiB4 images are downloaded at several times the size a phone draws them, for example Screenshot_2025-08-01_at_8.19.24_AM_1600x.png at 1,600 px wide, shown at 390 px. Resized copies would save about 166 KiB.
About 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 60 images in the HTML carry an alt attribute.
49 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: 49 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (188 characters)
Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/WritualShopify.png")”.
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
161 internal links, 29 external
The homepage links to 161 pages on writualplanner.com and 29 external pages.
5 checks passed
Title: 65 characters
Your title is a healthy 65 characters: “Writual Planner | Tarot Journals for Self-Care and Self-Discovery”.
Canonical URL set
The canonical URL is https://writualplanner.com/.
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://writualplanner.com/sitemap.xml.
AI search readiness
No llms.txt
There is no /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.
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.
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 (1,086 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a meta description
/blogs/news and /collections/all-products use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
/pages/shipping and /pages/about 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 54 found) and read each the way a search engine does.
6 checks passed
Linked pages load
6 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.
Every page has a meta description
All 6 pages that loaded have a meta description.
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 6 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 45 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 808 words of copy
The homepage carries about 808 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “SHOP NOW”.
15 calls to action
The homepage has 15 calls to action, for example “Shop”, “Shop Show menu” and “SHOP NOW”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
10 other companies contacted
Loading the homepage contacts 10 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 writualplanner.com, 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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Rebuy Personalization Engine · Klaviyo Email Marketing Sms · Triplewhale · Yotpo Product Reviews · Attentive · Okendo · Yotpo Loyalty Rewards · gorgias.chat · rechargecdn.com · attn.tv · 9gtb.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
- 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 19 issues on writualplanner.com, including 3 speed issues, 4 SEO issues and 3 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.