Website review, no card needed
stationeryhq.com website review
Visit site (opens in a new tab)Reviewed 8 November 202649 issues · 91 checks
This review found 49 issues worth fixing on stationeryhq.com, 24 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
72C- #96,933 of 125,344 reviewed websitesbeats 19%
- #59,529 of 70,165 online storesbeats 12%
- #55,408 of 63,753 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 938 ms |
| May 23, 2026 | 897 ms |
| May 30, 2026 | 891 ms |
| Jun 6, 2026 | 991 ms |
| Jun 13, 2026 | 990 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 968 ms |
| Jul 4, 2026 | 929 ms |
| Jul 11, 2026 | 911 ms |
| Jul 18, 2026 | 909 ms |
| Jul 25, 2026 | 972 ms |
| Aug 1, 2026 | 936 ms |
| Aug 8, 2026 | 876 ms |
| Aug 15, 2026 | 872 ms |
| Aug 22, 2026 | 873 ms |
| Aug 29, 2026 | 873 ms |
| Sep 5, 2026 | 978 ms |
| Sep 12, 2026 | 969 ms |
| Sep 19, 2026 | 952 ms |
| Sep 26, 2026 | 998 ms |
| Oct 3, 2026 | 922 ms |
| Oct 10, 2026 | 911 ms |
| Oct 17, 2026 | 926 ms |
| Oct 24, 2026 | 888 ms |
| Oct 31, 2026 | 898 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 71 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 70 ms |
| Jun 20, 2026 | 69 ms |
| Jun 27, 2026 | 65 ms |
| Jul 4, 2026 | 66 ms |
| Jul 11, 2026 | 70 ms |
| Jul 18, 2026 | 70 ms |
| Jul 25, 2026 | 71 ms |
| Aug 1, 2026 | 72 ms |
| Aug 8, 2026 | 69 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 70 ms |
| Aug 29, 2026 | 67 ms |
| Sep 5, 2026 | 69 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 71 ms |
| Sep 26, 2026 | 78 ms |
| Oct 3, 2026 | 97 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 71 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
7.1 s · 1.2 MB11 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.1 s faster on a phone.
Reduce unused JavaScript
6.9 s · 959 KiBAbout 959 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Shopify and others), adding 2.7 MB and 667 ms of main-thread time.
Render-blocking requests
900 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
YouTube adds 371 ms
371 msYouTube costs a phone 371 ms of main-thread work and 1.7 MB 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.
Use efficient cache lifetimes
350 ms · 78 KiB7 files are served with short cache lifetimes, so returning visitors download them again (78 KiB).
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 61 ms
61 msShopify costs a phone 61 ms of main-thread work and 664 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 169 ms. During a long task the page ignores taps.
Minify JavaScript
50 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
Reduce unused CSS
52 KiBAbout 52 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).
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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 10.6 s
10.6 sThe first text or image appears after 10.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.7 s
26.7 sYour largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Invitations & Stationery”.
Time to Interactive: 28.8 s
28.8 sThe page becomes fully interactive after 28.8 s. Good is under 3.8 s.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.46
0.46The layout shifts by 0.46 while loading, so content jumps under the reader's thumb. Good is under 0.1.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 227 ms
227 msScripts block taps and scrolling for 227 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 71 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 60 ms
60 msReal visitors wait 60 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (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: 307 ms
307 msReal visitors wait 307 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.6 MB in 262 requests
5.6 MBYour homepage downloads 5.6 MB in 262 requests on a phone: scripts 2.4 MB (69), images 1.6 MB (15) and other files 1.1 MB (153). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Wedding_Slider_copy_2048x.png weighs 562 KiB. On a phone connection a single image that size takes seconds.
6 images far larger than shown
695 KiB6 images are downloaded at several times the size a phone draws them, for example Wedding_Slider_copy_2048x.png at 1,940 px wide, shown at 341 px. Resized copies would save about 695 KiB.
6 images below the first screen load straight away
6 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.2 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
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
4 links inside paragraphs rely on colour alone to stand out.
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
3 H1 headlines
There are 3 <h1> headlines (“”, “Hey Creatives, Create a Wholesale Account & Save …” and “Who are we and what can we do for you?”). One clear main headline is easier for people and search engines.
Structured data has 2 problems
Structured data found (Organization) but with 2 problems, for example “Organization: missing name”.
137 internal links, 11 external
The homepage links to 137 pages on stationeryhq.com and 11 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.stationeryhq.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://www.stationeryhq.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, logo 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.
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 (814 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.stationeryhq.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a title
https://www.stationeryhq.com/pages/accessibility-statement, https://www.stationeryhq.com/collections, https://www.stationeryhq.com/collections/wrapping-paper-sheets, https://www.stationeryhq.com/pages/invitations-and-stationery, https://www.stationeryhq.com/collections/books and https://www.stationeryhq.com/pages/books-and-journals and 9 others have no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.stationeryhq.com/pages/wedding-supplies is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 pages without a meta description
https://www.stationeryhq.com/pages/accessibility-statement, https://www.stationeryhq.com/collections, https://www.stationeryhq.com/collections/wrapping-paper-sheets, https://www.stationeryhq.com/pages/invitations-and-stationery, https://www.stationeryhq.com/collections/books and https://www.stationeryhq.com/pages/books-and-journals and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.stationeryhq.com/pages/wedding-supplies has 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 50 found) and read each the way a search engine does.
2 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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25150321&Ver=2&mid=67419365-1226-4d81-bd8d-0fe9904a8490&bo=1&sid=e0208060db5111f1a782b76992b08d33&vid=e0209d10db5111f19ceb5bd80f8998e9&vids=1&msclkid=N&pi=918639831&lg.
13 small tap targets
13 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 569 words of copy
The homepage carries about 569 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE ABOUT SHQ”.
6 calls to action
The homepage has 6 calls to action, for example “Book Printing”, “Request Quote on Custom Project” and “Learn More About SHQ”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Ads (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 1 of them by other companies (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.
37 other companies contacted
Loading the homepage contacts 37 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 stationeryhq.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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Gdpr Backpack · Seokart · Forms · productcustomizer.com · b-cdn.net · gorgias.chat · 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
- Analytics
- Google Analytics
- Hosting
- Shopify
Company
- Headquarters
- Fremont
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on stationeryhq.com, including 16 speed issues, 4 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.