Website review, no card needed
thatwasepic.com website review
Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 68 checks
This review found 25 issues worth fixing on thatwasepic.com, 6 of them high impact, across 68 checks. The most urgent: page weight: 14.8 MB in 155 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
81B- #35,237 of 103,826 reviewed websitesbeats 60%
- #23,183 of 57,943 online storesbeats 53%
- #22,352 of 52,750 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 912 ms |
| May 23, 2026 | 858 ms |
| May 30, 2026 | 774 ms |
| Jun 6, 2026 | 774 ms |
| Jun 13, 2026 | 757 ms |
| Jun 20, 2026 | 782 ms |
| Jun 27, 2026 | 860 ms |
| Jul 4, 2026 | 857 ms |
| Jul 11, 2026 | 868 ms |
| Jul 18, 2026 | 924 ms |
| Jul 25, 2026 | 876 ms |
| Aug 1, 2026 | 942 ms |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 999 ms |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 998 ms |
| Oct 3, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 77 ms |
| May 23, 2026 | 70 ms |
| May 30, 2026 | 72 ms |
| Jun 6, 2026 | 72 ms |
| Jun 13, 2026 | 71 ms |
| Jun 20, 2026 | 72 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 71 ms |
| Jul 11, 2026 | 72 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 71 ms |
| Aug 1, 2026 | 72 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 75 ms |
| Aug 22, 2026 | 82 ms |
| Aug 29, 2026 | 83 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.5 s
1.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.3 s
3.8 s
Speed
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
550 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Use efficient cache lifetimes
350 ms · 30 KiB3 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).
Reduce unused CSS
300 ms · 60 KiBAbout 60 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.
Improve image delivery
150 ms · 64 KiB3 images could be 64 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
150 ms · 34 KiBAbout 34 KiB of JavaScript is downloaded but never used on this page. 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 65 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Shopify and Bugsnag), adding 74 KiB and 36 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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 302 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.5 s
5.5 sThe page becomes fully interactive after 5.5 s. Good is under 3.8 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 77 ms to 83 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 14.8 MB in 155 requests
14.8 MBYour homepage downloads 14.8 MB in 155 requests on a phone: media 13.4 MB (1), other files 823 KiB (110) and images 259 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 4.2 g of CO₂ per visit
4.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.20 g of CO₂e: 504.4 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
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 3 mores 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
36 internal links, 15 external
The homepage links to 36 pages on thatwasepic.com and 15 external pages.
6 checks passed
Title: 31 characters
Your title is a healthy 31 characters: “ThatWasEpic – That Was Epic LLC”.
Canonical URL set
The canonical URL is https://thatwasepic.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://thatwasepic.com/sitemap.xml.
AI search readiness
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.
llms.txt published
The site publishes https://thatwasepic.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://thatwasepic.com/collections/all-products-1, https://thatwasepic.com/collections/back-to-school, https://thatwasepic.com/collections/the-classics, https://thatwasepic.com/collections/tees, https://thatwasepic.com/collections/hoodies and https://thatwasepic.com/collections/crewnecks and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://thatwasepic.com/pages/help-center and https://thatwasepic.com/pages/contact-1 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 and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
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 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 51 words
The homepage has only about 51 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 THE COLLECTION”.
9 calls to action
The homepage has 9 calls to action, for example “SHOP BY STYLE”, “SHOP BY STYLE Show menu” and “SHOP THE COLLECTION”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Privacy and tracking
6 cookies set on arrival
6Opening the homepage sets 6 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.
4 other companies contacted
Loading the homepage contacts 4 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 thatwasepic.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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 25 issues on thatwasepic.com, including 9 speed issues, 2 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.