Website review, no card needed
byltbasics.com website review
Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 84 checks
This review found 33 issues worth fixing on byltbasics.com, 12 of them high impact, across 84 checks. The most urgent: page weight: 41.2 MB in 324 requests. 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
80B- #46,024 of 116,783 reviewed websitesbeats 55%
- #30,831 of 66,827 online storesbeats 47%
- #29,670 of 60,961 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 196 ms |
| May 23, 2026 | 194 ms |
| May 30, 2026 | 194 ms |
| Jun 6, 2026 | 195 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 195 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 198 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 191 ms |
| Sep 5, 2026 | 183 ms |
| Sep 12, 2026 | 179 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 189 ms |
| Oct 31, 2026 | 188 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
Speed
Reduce unused JavaScript
1.4 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.5 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Improve image delivery
1.1 s · 284 KiB5 images could be 284 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 4.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, alia-prod.com and Google Tag Manager and others), adding 38.3 MB and 2.0 s of main-thread time.
Shopify adds 805 ms
805 msShopify costs a phone 805 ms of main-thread work and 36.7 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.
Use efficient cache lifetimes
1.3 MB57 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
alia-prod.com adds 367 ms
367 msalia-prod.com costs a phone 367 ms of main-thread work and 247 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.
Google Tag Manager adds 309 ms
309 msGoogle Tag Manager costs a phone 309 ms of main-thread work and 482 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 · 59 KiBAbout 59 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 198 ms. During a long task the page ignores taps.
Legacy JavaScript
78 KiBPolyfills for old browsers add 78 KiB JavaScript that modern phones do not need.
Minify JavaScript
16 KiB16 KiB could be saved by minifying JavaScript.
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: 53 ms
53 msYour server sent the HTML in 53 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: 36.5 s
36.5 sThe page becomes fully interactive after 36.5 s. Good is under 3.8 s.
Speed Index: 12.8 s
12.8 sVisually, the page fills in at 12.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man in white and light tan outfit”.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 596 ms
596 msScripts block taps and scrolling for 596 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 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.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 196 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 194 ms
194 msReal visitors wait 194 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.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.037
0.037The layout barely moves while loading (CLS 0.037, good is under 0.1).
Images and page weight
Page weight: 41.2 MB in 324 requests
41.2 MBYour homepage downloads 41.2 MB in 324 requests on a phone: media 35.3 MB (6), scripts 3.6 MB (113) and other files 1.3 MB (151). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 11.7 g of CO₂ per visit
11.69 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.69 g of CO₂e: 1402.6 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
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
Headings skip levels
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.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“30% OFF SITEWIDE & STOREWIDE”, “BYLT Holiday 2026 Digital Catalog” and “Best Sellers”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization and WebPage) but with 1 problem, for example “Organization: sameAs is an empty list”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
36 internal links, 10 external
The homepage links to 36 pages on byltbasics.com and 10 external pages.
5 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “Shop BYLT premium essentials. Elevated tees, polos, joggers, and everyday staples designed for comfort, fit, and versat…”.
Title: 55 characters
Your title is a healthy 55 characters: “BYLT | Premium Modern Essentials for Men & Women | BYLT”.
Canonical URL set
The canonical URL is https://byltbasics.com/.
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://byltbasics.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://byltbasics.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (181 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a meta description
https://byltbasics.com/collections/holiday-shop, https://byltbasics.com/pages/everyday-denim-collection-lookbook, https://byltbasics.com/collections/holiday-shop-women, https://byltbasics.com/collections/bylt-holiday-2026-catalog, https://byltbasics.com/collections/mens-best-sellers and https://byltbasics.com/pages/bylt-for-life use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://byltbasics.com/pages/bylt-for-life has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://byltbasics.com/pages/bylt-for-life has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
5 pages slow to respond
https://byltbasics.com/collections/long-sleeve, https://byltbasics.com/collections/jackets-outerwear, https://byltbasics.com/collections/bylt-holiday-2026-catalog, https://byltbasics.com/collections/womens-best-sellers and https://byltbasics.com/pages/bylt-for-life took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 20 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 “Failed to load resource: net::ERR_FAILED”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 184 words
The homepage has only about 184 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “HOLIDAY HEAD START | 30% OFF SITEWIDE” and “UP TO 65% OFF LAST CALL STYLES”.
5 calls to action
The homepage has 5 calls to action, for example “Holiday Head Start | 30% OFF SITEWIDE”, “Up to 65% Off Last Call Styles” and “Last Call”.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Privacy and tracking
16 cookies set on arrival
16Opening the homepage sets 16 cookies (measured from a US location before any click).
34 other companies contacted
Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 byltbasics.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Swym Wishlist Plus
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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Costa Mesa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on byltbasics.com, including 18 speed issues, 4 SEO issues and 3 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.