Website review, no card needed
ghospell.com website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 85 checks
This review found 38 issues worth fixing on ghospell.com, 10 of them high impact, across 85 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
Site score
79C- #39,763 of 88,915 reviewed websitesbeats 50%
- #24,374 of 46,303 online storesbeats 42%
- #23,197 of 41,564 Shopify storesbeats 38%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 951 ms |
| May 23, 2026 | 939 ms |
| May 30, 2026 | 939 ms |
| Jun 6, 2026 | 944 ms |
| Jun 13, 2026 | 896 ms |
| Jun 20, 2026 | 885 ms |
| Jun 27, 2026 | 894 ms |
| Jul 4, 2026 | 871 ms |
| Jul 11, 2026 | 863 ms |
| Jul 18, 2026 | 859 ms |
| Jul 25, 2026 | 845 ms |
| Aug 1, 2026 | 853 ms |
| Aug 8, 2026 | 870 ms |
| Aug 15, 2026 | 887 ms |
| Aug 22, 2026 | 925 ms |
| Aug 29, 2026 | 979 ms |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 977 ms |
| Oct 3, 2026 | 890 ms |
| Oct 10, 2026 | 879 ms |
| Oct 17, 2026 | 892 ms |
| Oct 24, 2026 | 921 ms |
| Oct 31, 2026 | 943 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 84 ms |
| May 23, 2026 | 85 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 85 ms |
| Jun 27, 2026 | 84 ms |
| Jul 4, 2026 | 82 ms |
| Jul 11, 2026 | 81 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 82 ms |
| Aug 1, 2026 | 84 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 90 ms |
| Sep 5, 2026 | 92 ms |
| Sep 12, 2026 | 92 ms |
| Sep 19, 2026 | 91 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 84 ms |
| Oct 10, 2026 | 84 ms |
| Oct 17, 2026 | 83 ms |
| Oct 24, 2026 | 85 ms |
| Oct 31, 2026 | 88 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
Speed
Use efficient cache lifetimes
850 ms · 500 KiB27 files are served with short cache lifetimes, so returning visitors download them again (500 KiB).
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
730 ms · 257 KiBAbout 257 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 730 ms faster on a phone.
Improve image delivery
200 ms · 626 KiB5 images could be 626 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
600 ms · 107 KiBAbout 107 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 750 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Hexton adds 104 ms
104 msHexton costs a phone 104 ms of main-thread work and 422 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.
8 third-party services on the page
8 third-party services load with your homepage (Hexton, Shopify and theraptormedia.com and others), adding 731 KiB and 259 ms of main-thread time.
Legacy JavaScript
150 ms · 16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 71 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).
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 JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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 image.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Time to Interactive: 5.3 s
5.3 sThe page becomes fully interactive after 5.3 s. Good is under 3.8 s.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.101
0.101The layout shifts by 0.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 84 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 104 ms
104 msReal visitors wait 104 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 446 ms
446 msReal visitors wait 446 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 21 ms
21 msScripts block the page for only 21 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.0 MB in 173 requests
4.0 MBYour homepage downloads 4.0 MB in 173 requests on a phone: images 2.1 MB (15), scripts 912 KiB (55) and other files 734 KiB (89). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.14 g of CO₂e: 136.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (2 elements)
ARIA toggle fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (12 characters)
Your title is only 12 characters: “Ghospell.com”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
66 internal links, 5 external
The homepage links to 66 pages on ghospell.com and 5 external pages.
6 checks passed
Meta description: 92 characters
Your meta description is 92 characters: “GHOSPELL is a London-based fashion brand that explores urban elements of a modern lifestyle.”.
One H1 headline
Your main headline reads: “Ghospell”.
Canonical URL set
The canonical URL is https://ghospell.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://ghospell.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.
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.
2 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 (233 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
/collections/prime-time 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 38 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.
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
3 broken images
3 images failed to load on a phone, for example https://ghospell.com/.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://theraptormedia.com/instagram/instagram.css' from origin 'https://ghospell.com' has…”.
2 checks passed
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
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.
Only about 154 words
The homepage has only about 154 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NEW IN”.
2 calls to action
The homepage has 2 calls to action, for example “SHOP NEW IN” and “Contact”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
33 other companies contacted
Loading the homepage contacts 33 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 ghospell.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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
chimpstatic.com · rakutenadvertising.io · amazonaws.com · hextom.com · useamp.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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on ghospell.com, including 15 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.