sabertheory.com website review

A phone's processor spends 4.8 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (askflow.ai, loox.io and Shopify and others), adding 4.5 MB and 1.3 s of main-thread time.

Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.

askflow.ai costs a phone 744 ms of main-thread work and 1.4 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.

About 703 KiB of JavaScript is downloaded but never used on this page.

10 images could be 556 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

loox.io costs a phone 219 ms of main-thread work and 830 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.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

Shopify costs a phone 109 ms of main-thread work and 1.8 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.

The page has 2,303 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

23 files are served with short cache lifetimes, so returning visitors download them again (160 KiB).

8 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.

About 68 KiB of CSS is downloaded but never applied on this page.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

7 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

The page becomes fully interactive after 24.1 s. Good is under 3.8 s.

Visually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BLACK FRIDAY SALE!”. Most of its time is element render delay (2.5 s).

4 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 150 ms to 155 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 429 requests on a phone: scripts 2.2 MB (136), images 2.2 MB (85) and other files 1.0 MB (179). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example join.png at 1,920 px wide, shown at 390 px. Resized copies would save about 479 KiB.

4 images further down the page (272 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (72 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.

By the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 203.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

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.

ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 15 characters: “TheSaberCompany”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“”, “GALAXY'S FINEST SABERS” and “GALAXY'S FINEST SABERS”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 129 pages on sabertheory.com and 18 external pages.

https://thesabercompany.com/pages/build-your-bundle, https://thesabercompany.com/collections/collection-jl, https://thesabercompany.com/pages/saber-for-kids and https://thesabercompany.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

https://thesabercompany.com/collections/best-sellers-sabers, https://thesabercompany.com/collections/collection-jl, https://thesabercompany.com/collections/all and https://thesabercompany.com/products/youngling-saber have no <h1> headline, so visitors and search engines get no clear main topic.

https://thesabercompany.com/products/padawan-saber, https://thesabercompany.com/products/revan-saber and https://thesabercompany.com/products/youngling-saber took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,237 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 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.

Opening the homepage sets 23 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.