Website review, no card needed
thea3b.com website review
Visit site (opens in a new tab)Reviewed 16 November 202648 issues · 76 checks
This review found 48 issues worth fixing on thea3b.com, 19 of them high impact, across 76 checks. The most urgent: improve image delivery. 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
64D- #106,816 of 113,406 reviewed websitesbeats 5%
- #63,588 of 65,377 online storesbeats 2%
- #58,466 of 59,798 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
9.9 s · 2.0 MB2 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.9 s faster on a phone.
Use efficient cache lifetimes
8.6 s · 1.7 MB26 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Reduce unused JavaScript
1.5 s · 297 KiBAbout 297 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.0 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.0 s.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and teepublic.com and others), adding 924 KiB and 742 ms of main-thread time.
Google Tag Manager adds 295 ms
295 msGoogle Tag Manager costs a phone 295 ms of main-thread work and 356 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.
Other Google APIs/SDKs adds 282 ms
282 msOther Google APIs/SDKs costs a phone 282 ms of main-thread work and 142 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 759 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
teepublic.com adds 142 ms
142 msteepublic.com costs a phone 142 ms of main-thread work and 398 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 CSS
150 ms · 40 KiBAbout 40 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.
Legacy JavaScript
150 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
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: 436 ms
436 msYour server sent the HTML in 436 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 17.8 s
17.8 sYour largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ISTANABET | THEA3B - Toko Fashion Streetwear Terbaru Jual T…”.
Speed Index: 14.5 s
14.5 sVisually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.8 s
17.8 sThe page becomes fully interactive after 17.8 s. Good is under 3.8 s.
Total Blocking Time: 354 ms
354 msScripts block taps and scrolling for 354 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
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.
1 checks passed
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
1 image over 500 KB
banner.png weighs 2.1 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
642 KiB1 image is downloaded at several times the size a phone draws it, for example banner.png at 1,254 px wide, shown at 350 px. Resized copies would save about 642 KiB.
Page weight: 3.1 MB in 42 requests
3.1 MBYour homepage downloads 3.1 MB in 42 requests on a phone: images 2.2 MB (20), scripts 652 KiB (13) and fonts 142 KiB (4). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (2.1 MB) 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.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
33 images without alt text
33 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 10 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.
Title is long (96 characters)
Your title is 96 characters, so Google will cut it off around 60: “ISTANABET | THEA3B - Toko Fashion Streetwear Terbaru Jual Trackpants & Outfit Casual Pria…”.
2 H1 headlines
There are 2 <h1> headlines (“ISTANABET | THEA3B - Toko Fashion Streetwear Terb…” and “ISTANABET | THEA3B - Toko Fashion Streetwear Terb…”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, FAQPage and Product) but with 1 problem, for example “Product: logo is not an absolute URL ("https://thea3b.com/assets/banner.png")”.
No robots.txt
There is no robots.txt at thea3b.com/robots.txt, the first file search crawlers ask for.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
120 internal links, 20 external
The homepage links to 120 pages on thea3b.com and 20 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.thea3b.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://thea3b.com/sitemap.xml.
AI search readiness
Snippets are switched off
The robots meta tag says “index, follow, nosnippet”, which tells Google, Bing and the AI answers built on them not to quote this page.
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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (919 words), so crawlers that don't run JavaScript still read it.
Other pages
11 linked pages are broken
Your homepage links to https://thea3b.com/about, https://thea3b.com/intellectual-property-policy, https://thea3b.com/ccpa, https://thea3b.com/privacy_policy, https://thea3b.com/terms and https://thea3b.com/social-responsibility and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
Best practices
7 broken images
7 images failed to load on a phone, for example https://assets.teepublic.com/assets/teepublicons/x_close_orange400-c1926221e50e7f6686d23ac344405449054e43f23d0f3306f15d8dfd546f999a.svg.
5 small tap targets
5 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Unexpected end of input”.
15 distorted images
15 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 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 456 words of copy
The homepage carries about 456 words of visible text.
4 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Order Status”, “Contact Us” and “Artist Signup”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 36 testimonial or review blocks, 1 customer or partner logo, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
6 other companies contacted
Loading the homepage contacts 6 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 thea3b.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on thea3b.com, including 16 speed issues, 6 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.