Website review, no card needed

costumehalloween.com logo

costumehalloween.com website review

Visit site (opens in a new tab)Reviewed 10 November 202625 issues · 62 checks

This review found 25 issues worth fixing on costumehalloween.com, 7 of them high impact, across 62 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 costumehalloween.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix66
  • Improve image delivery

    1.3 s · 1.1 MB

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

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    450 ms · 114 KiB

    About 114 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.

  • Legacy JavaScript

    350 ms · 24 KiB

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

  • Render-blocking requests

    350 ms

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

  • Main-thread work: 2.4 s

    A phone's processor spends 2.4 s on main-thread work while loading, 1.2 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 (heatmap.com, StackAdapt and cloudfront.net and others), adding 345 KiB and 335 ms of main-thread time.

  • Use efficient cache lifetimes

    200 ms · 40 KiB

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

  • Reduce unused CSS

    150 ms · 41 KiB

    About 41 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.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 121 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

4 to fix67
  • 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.

  • Time to Interactive: 10.2 s

    10.2 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

    The first text or image appears after 2.5 s on a phone. Good is under 1.8 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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 57 ms

    57 ms

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

Images and page weight

1 to fix67
  • Page weight: 3.5 MB in 375 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 375 requests on a phone: other files 1.3 MB (256), images 1.3 MB (16) and scripts 659 KiB (81). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

Accessibility

4 to fixGoogle 9190
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 text elements with low contrast

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

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

  • Headings skip levels

    Headings skip levels (h2 → h6, h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 20 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10095
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Classic Halloween Costumes” and “Classic Halloween Costumes”). One clear main headline is easier for people and search engines.

  • 412 internal links, 0 external

    The homepage links to 412 pages on costumehalloween.com and 0 external pages.

7 checks passed
  • Meta description: 103 characters

    Your meta description is 103 characters: “Shop the Best Halloween Costumes Online in Canada - Your One-Stop Destination for All Things Halloween.”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Costumes Online | Halloween Costumes Canada”.

  • Canonical URL set

    The canonical URL is https://costumes.online/.

  • Structured data in place

    Structured data found: Organization and 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://costumes.online/sitemap.xml.

AI search readiness

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

  • llms.txt published

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

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://costumes.online/pages/blog, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://costumes.online/pages/halloween-costumes and https://costumes.online/collections/halloween-costumes all use the title “Halloween Costumes – Costumes Online”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://costumes.online/collections/all, https://costumes.online/pages/halloween-costumes, https://costumes.online/collections/halloween-costumes and https://costumes.online/collections/plus-size-halloween-costumes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://costumes.online/collections/girl-costumes and https://costumes.online/collections/boys-costumes 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 196 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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: 1 testimonial or review block. 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.

  • Only about 10 words

    The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

  • 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
  • 16 calls to action

    The homepage has 16 calls to action, for example “Subscribe”, “Contact Lenses” and “Shop Costumes”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • 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 costumehalloween.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gorgias Live Chat Helpdesk · 9gtb.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

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 25 issues on costumehalloween.com, including 10 speed issues, 1 SEO issue and 4 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