Website review, no card needed
namestories.com website review
Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 81 checks
This review found 34 issues worth fixing on namestories.com, 9 of them high impact, across 81 checks. The most urgent: page weight: 4.5 MB in 329 requests. 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
85B- #14,805 of 108,149 reviewed websitesbeats 82%
- #9,435 of 61,284 online storesbeats 79%
- #9,179 of 55,919 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.7 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.8 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 154 ms |
| May 23, 2026 | 156 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 172 ms |
| Jun 13, 2026 | 172 ms |
| Jun 20, 2026 | 157 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 156 ms |
| Jul 11, 2026 | 155 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 153 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 168 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 161 ms |
| Sep 12, 2026 | 160 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 175 ms |
| Oct 31, 2026 | 175 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
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Shopify and boostcommerce.io and others), adding 1.3 MB and 853 ms of main-thread time.
Render-blocking requests
700 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Klaviyo adds 363 ms
363 msKlaviyo costs a phone 363 ms of main-thread work and 632 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
402 KiBAbout 402 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
384 KiB39 images could be 384 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 337 ms
337 msShopify costs a phone 337 ms of main-thread work and 411 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
50 ms · 105 KiB19 files are served with short cache lifetimes, so returning visitors download them again (105 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 94 ms. During a long task the page ignores taps.
Reduce unused CSS
62 KiBAbout 62 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “personalized name print gifts”.
Time to Interactive: 12.0 s
12.0 sThe page becomes fully interactive after 12.0 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 154 ms to 175 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 179 ms
179 msReal visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 540 ms
540 msReal visitors wait 540 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, good is under 0.1).
Total Blocking Time: 60 ms
60 msScripts block the page for only 60 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.5 MB in 329 requests
4.5 MBYour homepage downloads 4.5 MB in 329 requests on a phone: images 2.0 MB (71), scripts 1.2 MB (110) and other files 925 KiB (101). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BoyPlayingwBlocks-OnBed-Frontview-4x5Ratio-Vertical-MockupDe 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).
1 image far larger than shown
78 KiB1 image is downloaded at several times the size a phone draws it, for example 16c5a818-c2e7-4555-b6d3-ada165eeee09.png at 2,150 px wide, shown at 239 px. Resized copies would save about 78 KiB.
1 image in older formats
1 image (87 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 1.3 g of CO₂ per visit
1.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.27 g of CO₂e: 152.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
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.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails 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
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Unique Personalized Gifts | Name Meaning Art and Prints | Name Stories”.
Meta description is long (222 characters)
Your meta description is 222 characters; Google truncates after about 160, so the end of your pitch is cut.
63 internal links, 0 external
The homepage links to 63 pages on namestories.com and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Personalized Name Meaning Gifts”.
Canonical URL set
The canonical URL is https://namestories.com/.
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://namestories.com/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 (1,145 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://namestories.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://namestories.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://namestories.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://namestories.com/customer_authentication/redirect, https://namestories.com/policies/shipping-policy and https://namestories.com/pages/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://namestories.com/pages/about-us and https://namestories.com/pages/about-our-products use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://namestories.com/collections/all, https://namestories.com/customer_authentication/redirect, https://namestories.com/pages/contact-us and https://namestories.com/pages/about-us 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 37 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.
Titles are unique
Every page we checked has its own title.
Best practices
19 small tap targets
19 of 33 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 “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 108 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,017 words of copy
The homepage carries about 1,017 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 NOW”.
8 calls to action
The homepage has 8 calls to action, for example “Contact Us”, “SHOP NOW” and “New Name Request”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
47 other companies contacted
Loading the homepage contacts 47 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 namestories.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Superspeed Web Vitals · Judge Me Reviews · Shopclimb Trust Badges · Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Product Filter Search · goaffpro.com · hulkapps.com · gorgias.chat · shareasale.com · hextom.com · cloudfront.net · 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
- React
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Corte Madera
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on namestories.com, including 12 speed issues, 2 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.