Website review, no card needed
everlast.com website review
Visit site (opens in a new tab)Reviewed 1 November 202634 issues · 81 checks
This review found 34 issues worth fixing on everlast.com, 9 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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- #37,156 of 109,569 reviewed websitesbeats 60%
- #24,779 of 62,042 online storesbeats 54%
- #23,908 of 56,575 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 114 ms |
| May 16, 2026 | 113 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 138 ms |
| Aug 22, 2026 | 142 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 149 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 157 ms |
| Oct 10, 2026 | 158 ms |
| Oct 17, 2026 | 161 ms |
| Oct 24, 2026 | 163 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.9 s
1.3 s
1.7 s
2.1 s
2.6 s
3.0 s
3.4 s
Speed
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,436 HTML elements
The page has 5,436 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 913 ms. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Yotpo, Klaviyo and Hotjar and others), adding 1.0 MB and 714 ms of main-thread time.
Render-blocking requests
700 ms17 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Yotpo adds 330 ms
330 msYotpo costs a phone 330 ms of main-thread work and 336 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 251 ms
251 msKlaviyo costs a phone 251 ms of main-thread work and 392 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
273 KiBAbout 273 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
150 ms · 241 KiB11 files are served with short cache lifetimes, so returning visitors download them again (241 KiB).
Improve image delivery
150 ms · 70 KiB4 images could be 70 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 CSS
46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
28 KiB28 KiB could be saved by minifying JavaScript.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
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
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.
Time to Interactive: 16.8 s
16.8 sThe page becomes fully interactive after 16.8 s. Good is under 3.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 357 ms
357 msReal visitors wait 357 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 114 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.4 s
4.4 sVisually, the page fills in at 4.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (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: 544 ms
544 msReal visitors wait 544 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.049
0.049The layout barely moves while loading (CLS 0.049, good is under 0.1).
Images and page weight
Page weight: 3.8 MB in 363 requests
3.8 MBYour homepage downloads 3.8 MB in 363 requests on a phone: images 1.6 MB (86), scripts 1,006 KiB (93) and other files 724 KiB (133). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
17 KiB1 image is downloaded at several times the size a phone draws it, for example PDP_Below_the_fold_1.png at 400 px wide, shown at 116 px. Resized copies would save about 17 KiB.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Certain ARIA roles must be contained by particular parents (3 elements)
Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (18 elements)
ARIA role should be appropriate for the element: 18 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 171 images in the HTML carry an alt attribute.
52 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: 52 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
One H1 headline
Your <h1> is empty.
436 internal links, 29 external
The homepage links to 436 pages on everlast.com and 29 external pages.
7 checks passed
Meta description: 103 characters
Your meta description is 103 characters: “Trusted by champions since 1910. Boxing gloves, punching bags, training apparel & more – built to last.”.
Title: 30 characters
Your title is a healthy 30 characters: “Everlast | Greatness is Within”.
Canonical URL set
The canonical URL is https://www.everlast.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://www.everlast.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 (2,534 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.everlast.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://www.everlast.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.everlast.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://www.everlast.com/collections/all, https://www.everlast.com/customer_authentication/redirect and https://www.everlast.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.everlast.com/collections/boxing-gloves-for-beginners/gloves+boxing, whose canonical is https://www.everlast.com/collections/boxing-gloves-for-beginners/boxing+gloves. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.everlast.com/customer_authentication/redirect 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 154 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.
Titles are unique
Every page we checked has its own title.
Best practices
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.”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
49 of 49 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 505 words of copy
The homepage carries about 505 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: “SHOP NOW”.
45 calls to action
The homepage has 45 calls to action, for example “SHOP ALL BOXING”, “Shop All” and “SHOP ALL MMA”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Hotjar and Klaviyo (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
22 other companies contacted
Loading the homepage contacts 22 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 everlast.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Founded
- 1910
- Headquarters
- New York City
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 everlast.com, including 17 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.