Website review, no card needed

cosplaybuzz.com logo

cosplaybuzz.com website review

Visit site (opens in a new tab)Reviewed 8 November 202627 issues · 80 checks

This review found 27 issues worth fixing on cosplaybuzz.com, 10 of them high impact, across 80 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

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.1 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.5 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
149 ms108 msMay 16Oct 31128 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026113 ms
May 23, 2026127 ms
May 30, 2026129 ms
Jun 6, 2026132 ms
Jun 13, 2026130 ms
Jun 20, 2026123 ms
Jun 27, 2026121 ms
Jul 4, 2026122 ms
Jul 11, 2026132 ms
Jul 18, 2026144 ms
Jul 25, 2026137 ms
Aug 1, 2026139 ms
Aug 8, 2026130 ms
Aug 15, 2026130 ms
Aug 22, 2026129 ms
Aug 29, 2026128 ms
Sep 5, 2026127 ms
Sep 12, 2026124 ms
Sep 19, 2026124 ms
Sep 26, 2026123 ms
Oct 3, 2026129 ms
Oct 10, 2026130 ms
Oct 17, 2026132 ms
Oct 24, 2026134 ms
Oct 31, 2026128 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

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

How it loaded on a phone

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

Speed

8 to fix60
  • Improve image delivery

    1.4 s · 2.2 MB

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

  • Render-blocking requests

    3.5 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.

  • 3,542 HTML elements

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused JavaScript

    660 ms · 234 KiB

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

  • Legacy JavaScript

    300 ms · 21 KiB

    Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Shopify adds 152 ms

    152 ms

    Shopify costs a phone 152 ms of main-thread work and 316 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.

  • cdn-spurit.com adds 133 ms

    133 ms

    cdn-spurit.com costs a phone 133 ms of main-thread work and 338 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, cdn-spurit.com and Cloudflare and others), adding 723 KiB and 317 ms of main-thread time.

  • Reduce unused CSS

    190 ms · 41 KiB

    About 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 18 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.1 s

    10.1 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

    The first text or image appears after 4.4 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 10.1 s

    10.1 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 113 ms to 128 ms 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.4 s

    1.4 s

    Real visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 622 ms

    622 ms

    Real visitors wait 622 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 17% faster for real visitors

    -17%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 87 ms

    87 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 4.8 MB in 182 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 182 requests on a phone: images 3.2 MB (46), other files 713 KiB (70) and scripts 685 KiB (51). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.37 g

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

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9395
  • 88 text elements with low contrast

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

  • All page content should be contained by landmarks (13 elements)

    All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 19 links without text

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

2 checks passed
  • Every image has alt text

    All 99 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Buy Cosplay Wigs, Costumes, Shoes and Boots for Cosplayers – CosplayBuzz”.

  • Structured data has 4 problems

    Structured data found (Organization, Store and WebSite) but with 4 problems, for example “WebSite: url is not an absolute URL ("www.cosplaybuzz.com")”.

  • No social preview image

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

  • One H1 headline

    Your <h1> is empty.

  • 221 internal links, 8 external

    The homepage links to 221 pages on cosplaybuzz.com and 8 external pages.

4 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Best Quality Lace Wigs for Cosplay. Custom Made Wig Service Available. Best Deal! 100% satisfaction Guarantee! Buy Outf…”.

  • Canonical URL set

    The canonical URL is https://www.cosplaybuzz.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://www.cosplaybuzz.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.cosplaybuzz.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.

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.

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://www.cosplaybuzz.com/collections/game-costume, https://www.cosplaybuzz.com/collections/film-tv-costume, https://www.cosplaybuzz.com/collections/film-tv-wigs and https://www.cosplaybuzz.com/pages/by-series have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.cosplaybuzz.com/pages/by-series 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 121 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Error https://s2.cdn-spurit.com/shopify-apps/8upsell/store/442d844fe57fe3a9b95cb3f833f35ac2_v2.css?1750418814 [object E…”.

2 checks passed
  • Tap targets are thumb-sized

    177 of 182 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • Thin social proof

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,706 words of copy

    The homepage carries about 1,706 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”, “Order Processing” and “Subscribe”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.

  • 9 cookies set on arrival

    9

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

  • 13 other companies contacted

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

Apps your storefront loads

Oxi Social Login Wishlist · Xcloud Search Filter · Judge Me Reviews · Seo Manager Venntov · Instafeed · Restockrocket · cloudfront.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

E-commerce
Shopify
Hosting
Cloudflare

Company

Headquarters
Vancouver

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on cosplaybuzz.com, including 12 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

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