Website review, no card needed
mytitlestore.com website review
Visit site (opens in a new tab)Reviewed 16 November 202634 issues · 82 checks
This review found 34 issues worth fixing on mytitlestore.com, 10 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
82B- #33,154 of 117,615 reviewed websitesbeats 66%
- #22,156 of 66,923 online storesbeats 60%
- #21,424 of 61,018 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 100 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 86 ms |
| Jul 18, 2026 | 82 ms |
| Jul 25, 2026 | 85 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 95 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 80 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 102 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 98 ms |
| Oct 31, 2026 | 92 ms |
| Nov 7, 2026 | 84 ms |
| Nov 14, 2026 | 87 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.7 s
3.3 s
5.0 s
6.7 s
8.3 s
10.0 s
11.7 s
13.3 s
Speed
Reduce unused JavaScript
5.4 s · 674 KiBAbout 674 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.
Avoid multiple page redirects
2.9 sThe page goes through 3 redirects before it starts loading, costing about 2.9 s. Link and advertise the final URL directly.
8 third-party services on the page
8 third-party services load with your homepage (rebuyengine.com, Shopify and Google Tag Manager and others), adding 2.1 MB and 820 ms of main-thread time.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
rebuyengine.com adds 409 ms
409 msrebuyengine.com costs a phone 409 ms of main-thread work and 1.1 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.
Legacy JavaScript
400 ms · 71 KiBPolyfills for old browsers add 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Document request latency
300 msThe HTML itself could arrive about 300 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Shopify adds 126 ms
126 msShopify costs a phone 126 ms of main-thread work and 444 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.
1,636 HTML elements
The page has 1,636 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
200 ms · 51 KiB12 files are served with short cache lifetimes, so returning visitors download them again (51 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Reduce unused CSS
90 ms · 18 KiBAbout 18 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 90 ms faster on a phone.
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
Largest Contentful Paint: 22.7 s
22.7 sYour largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 329 ms
329 msScripts block taps and scrolling for 329 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 88 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 483 ms
483 msReal visitors wait 483 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.017
0.017The layout barely moves while loading (CLS 0.017, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 364 requests
4.3 MBYour homepage downloads 4.3 MB in 364 requests on a phone: scripts 1.9 MB (137), other files 1.2 MB (169) and images 555 KiB (15). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Nav_Square_-_MMA_Gloves.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.2 g of CO₂ per visit
1.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 145.9 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 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.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 141 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (71 characters)
Your title is 71 characters, so Google will cut it off around 60: “Wholesale Boxing Equipment | Bulk Discount Boxing Gear – My TITLE Store”.
Meta description is long (178 characters)
Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
251 internal links, 11 external
The homepage links to 251 pages on mytitlestore.com and 11 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://mytitlestore.com/.
Structured data in place
Structured data found: 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://mytitlestore.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,524 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mytitlestore.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://mytitlestore.com/pages/holiday-gift-guide, https://mytitlestore.com/collections/bag-gloves, https://mytitlestore.com/collections/competition-gloves, https://mytitlestore.com/collections/boxing-gloves, https://mytitlestore.com/collections/gloves-new-arrivals and https://mytitlestore.com/collections/gloves-top-sellers have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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
23 small tap targets
23 of 77 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 336 words of copy
The homepage carries about 336 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “APPLY HERE”.
23 calls to action
The homepage has 23 calls to action, for example “Shop All Gloves”, “Shop Now” and “Shop All Shoes”.
Social proof on the page
Social proof on the homepage: 58 testimonial or review blocks and 1 trust badge.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
28 other companies contacted
Loading the homepage contacts 28 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 mytitlestore.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Persistent Cart · Rebuy Personalization Engine · Cart Persistify · Simple Bundle · Gdpr Backpack · expivi.com · b-cdn.net
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
- Hosting
- Shopify
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 mytitlestore.com, including 15 speed issues, 4 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.