Website review, no card needed

kybrtees.com logo

kybrtees.com website review

Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 72 checks

This review found 31 issues worth fixing on kybrtees.com, 9 of them high impact, across 72 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of kybrtees.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kybrtees.com at 0.4 s0.4 s
  2. kybrtees.com at 0.8 s0.8 s
  3. kybrtees.com at 1.1 s1.1 s
  4. kybrtees.com at 1.5 s1.5 s
  5. kybrtees.com at 1.9 s1.9 s
  6. kybrtees.com at 2.3 s2.3 s
  7. kybrtees.com at 2.6 s2.6 s
  8. kybrtees.com at 3.0 s3.0 s

Speed

7 to fix74
  • Improve image delivery

    2.8 s · 2.7 MB

    24 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    900 ms

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

  • Reduce unused JavaScript

    450 ms · 167 KiB

    About 167 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Klaviyo, Shopify and JSDelivr CDN and others), adding 2.0 MB and 155 ms of main-thread time.

  • Shopify adds 64 ms

    64 ms

    Shopify costs a phone 64 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.

  • 2,208 HTML elements

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

  • Duplicated JavaScript

    150 ms · 38 KiB

    38 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    27 KiB

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

  • Reduce unused CSS

    16 KiB

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

  • Use efficient cache lifetimes

    14 KiB

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

  • 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.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 408 ms of it running JavaScript. That is comfortably low.

  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix67
  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 20.1 s

    20.1 s

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

  • Speed Index: 3.4 s

    3.4 s

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

  • 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.

3 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix42
  • Page weight: 8.5 MB in 267 requests

    8.5 MB

    Your homepage downloads 8.5 MB in 267 requests on a phone: images 6.9 MB (60), other files 807 KiB (100) and scripts 593 KiB (72). Under 2 MB keeps phones on slow connections fast.

  • 11 images far larger than shown

    1.5 MB

    11 images are downloaded at several times the size a phone draws them, for example website-banner-update-426.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 1.5 MB.

  • An image on the first screen is lazy-loaded

    website-banner-update-426.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 2.4 g of CO₂ per visit

    2.40 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 9093
  • 7 text elements with low contrast

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

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 55 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10091
  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • 153 internal links, 5 external

    The homepage links to 153 pages on kybrtees.com and 5 external pages.

6 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “Explore our range of vintage inspired clothing and exclusive graphic tees. Shop unique styles from iconic universes.”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “KYBER - Vintage and Streetwear Clothing – KYBR”.

  • Canonical URL set

    The canonical URL is https://kybrtees.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://kybrtees.com/sitemap.xml.

AI search readiness

100
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 (744 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    /customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    /customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 9 pages without a meta description

    /collections/all-tees, /collections/star-wars, /collections/marvel, /collections/dc, /collections/beyond and /collections/anime and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    /apps/parcelpanel and /customer_authentication/redirect have 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 50 found) and read each the way a search engine does.

3 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.

Best practices

2 to fixGoogle 9687
  • 14 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 52 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 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 259 words of copy

    The homepage carries about 259 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now” and “SHOP STAR WARS”.

  • 46 calls to action

    The homepage has 46 calls to action, for example “SHOP ALL”, “TRACK YOUR ORDER” and “Shop Now”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 kybrtees.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Seowill Ai Seo · Size Charts Jotly · Nitro Lookbook · Klaviyo Email Marketing Sms · Free Contact Form · zooomyapps.com

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

CMS
WordPress
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 31 issues on kybrtees.com, including 10 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25