Website review, no card needed
theorysabers.com website review
Visit site (opens in a new tab)Reviewed 8 November 202646 issues · 93 checks
This review found 46 issues worth fixing on theorysabers.com, 13 of them high impact, across 93 checks. The most urgent: mobile performance score: 45. 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
77C- #67,150 of 120,366 reviewed websitesbeats 39%
- #43,648 of 68,142 online storesbeats 31%
- #41,550 of 62,097 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 467 ms |
| May 23, 2026 | 471 ms |
| May 30, 2026 | 479 ms |
| Jun 6, 2026 | 499 ms |
| Jun 13, 2026 | 523 ms |
| Jun 20, 2026 | 543 ms |
| Jun 27, 2026 | 557 ms |
| Jul 4, 2026 | 564 ms |
| Jul 11, 2026 | 562 ms |
| Jul 18, 2026 | 547 ms |
| Jul 25, 2026 | 532 ms |
| Aug 1, 2026 | 537 ms |
| Aug 8, 2026 | 568 ms |
| Aug 15, 2026 | 589 ms |
| Aug 22, 2026 | 621 ms |
| Aug 29, 2026 | 613 ms |
| Sep 5, 2026 | 593 ms |
| Sep 12, 2026 | 599 ms |
| Sep 19, 2026 | 597 ms |
| Sep 26, 2026 | 603 ms |
| Oct 3, 2026 | 600 ms |
| Oct 10, 2026 | 716 ms |
| Oct 17, 2026 | 738 ms |
| Oct 24, 2026 | 772 ms |
| Oct 31, 2026 | 664 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
1.0 s
2.0 s
3.1 s
4.1 s
5.1 s
6.1 s
7.2 s
8.2 s
Speed
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.8 s
A phone's processor spends 6.8 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,269 HTML elements
The page has 3,269 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Freshchat, omnisnippet1.com and Google Tag Manager and others), adding 2.4 MB and 1.6 s of main-thread time.
Improve image delivery
100 ms · 1.6 MB22 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused JavaScript
620 ms · 949 KiBAbout 949 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 620 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 367 KiB21 files are served with short cache lifetimes, so returning visitors download them again (367 KiB).
Freshchat adds 404 ms
404 msFreshchat costs a phone 404 ms of main-thread work and 869 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.
Render-blocking requests
400 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
Google Tag Manager adds 261 ms
261 msGoogle Tag Manager costs a phone 261 ms of main-thread work and 352 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.
omnisnippet1.com adds 282 ms
282 msomnisnippet1.com costs a phone 282 ms of main-thread work and 119 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.
rebuyengine.com adds 176 ms
176 msrebuyengine.com costs a phone 176 ms of main-thread work and 333 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.
Klaviyo adds 142 ms
142 msKlaviyo costs a phone 142 ms of main-thread work and 309 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.
Duplicated JavaScript
250 ms · 141 KiB141 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
150 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 218 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 28 ms
28 msYour server sent the HTML in 28 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: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 32.7 s
32.7 sThe page becomes fully interactive after 32.7 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 751 ms
751 msScripts block taps and scrolling for 751 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 352 ms
352 msReal visitors wait 352 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 467 ms to 664 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 814 ms
814 msReal visitors wait 814 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.01
0.01The layout barely moves while loading (CLS 0.01, good is under 0.1).
Images and page weight
Page weight: 7.0 MB in 347 requests
7.0 MBYour homepage downloads 7.0 MB in 347 requests on a phone: images 3.1 MB (55), scripts 2.6 MB (135) and other files 950 KiB (132). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Homepage_-_Card_8.webp weighs 822 KiB. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (1.9 MB) are 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.
14 images below the first screen load straight away
14 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.0 g of CO₂ per visit
1.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.99 g of CO₂e: 239.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
10 images without alt text
10 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (13 characters)
Your title is only 13 characters: “Theory Sabers”. 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.
121 internal links, 2 external
The homepage links to 121 pages on theorysabers.com and 2 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Fulfill your destiny with unique design high quality sabers and accessories made by a fan for fans. Best saber store th…”.
One H1 headline
Your main headline reads: “Made by fans. For Fans.”.
Canonical URL set
The canonical URL is https://www.theorysabers.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.theorysabers.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.
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 (1,228 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.theorysabers.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://www.theorysabers.com/collections/all-products, https://www.theorysabers.com/pages/mystery-box, https://www.theorysabers.com/collections/merch, https://www.theorysabers.com/collections/accessories and https://www.theorysabers.com/collections/saber-bundles have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.theorysabers.com/collections/sabers, https://www.theorysabers.com/collections/all-products, https://www.theorysabers.com/collections/stands, https://www.theorysabers.com/collections/merch and https://www.theorysabers.com/collections/saber-bundles 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 49 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
19 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 760 words of copy
The homepage carries about 760 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP SABERS”.
6 calls to action
The homepage has 6 calls to action, for example “SHOP”, “Buy 1 Get 2 FREE Use code R2FREE” and “shop sabers”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 63 testimonial or review blocks, 30 customer or partner logos, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
31 cookies set on arrival
31Opening the homepage sets 31 cookies, 2 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.
46 other companies contacted
Loading the homepage contacts 46 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 theorysabers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on theorysabers.com, including 24 speed issues, 2 SEO issues and 2 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.