Website review, no card needed

crayola.com logo

crayola.com website review

Visit site (opens in a new tab)Reviewed 26 October 202651 issues · 90 checks

This review found 51 issues worth fixing on crayola.com, 16 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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
4.7 s1.2 sMay 9Oct 244.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20262.6 s
Sep 26, 20263.4 s
Oct 3, 20264.0 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Oct 24, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
159 ms107 msMay 9Oct 24146 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026120 ms
May 16, 2026119 ms
May 23, 2026118 ms
May 30, 2026116 ms
Jun 6, 2026116 ms
Jun 13, 2026115 ms
Jun 20, 2026114 ms
Jun 27, 2026115 ms
Jul 4, 2026114 ms
Jul 11, 2026113 ms
Jul 18, 2026113 ms
Jul 25, 2026113 ms
Aug 1, 2026114 ms
Aug 8, 2026115 ms
Aug 15, 2026116 ms
Aug 22, 2026117 ms
Aug 29, 2026119 ms
Sep 5, 2026120 ms
Sep 12, 2026121 ms
Sep 19, 2026129 ms
Sep 26, 2026139 ms
Oct 3, 2026147 ms
Oct 10, 2026153 ms
Oct 17, 2026149 ms
Oct 24, 2026146 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 crayola.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. crayola.com at 0.7 s0.7 s
  2. crayola.com at 1.5 s1.5 s
  3. crayola.com at 2.2 s2.2 s
  4. crayola.com at 2.9 s2.9 s
  5. crayola.com at 3.6 s3.6 s
  6. crayola.com at 4.4 s4.4 s
  7. crayola.com at 5.1 s5.1 s
  8. crayola.com at 5.8 s5.8 s

Speed

13 to fix27
  • Render-blocking requests

    13.6 s

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

  • Reduce unused CSS

    11.4 s · 2.1 MB

    About 2.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 11.4 s faster on a phone.

  • Use efficient cache lifetimes

    6.6 s · 1.4 MB

    47 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

  • Reduce unused JavaScript

    4.2 s · 866 KiB

    About 866 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Mobile performance score: 27

    27/100

    Your mobile performance score is 27 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    500 ms · 1.6 MB

    22 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Listrak and others), adding 2.4 MB and 1.6 s of main-thread time.

  • YouTube adds 605 ms

    605 ms

    YouTube costs a phone 605 ms of main-thread work and 992 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 502 ms

    502 ms

    Google Tag Manager costs a phone 502 ms of main-thread work and 357 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.

  • Minify JavaScript

    440 ms · 60 KiB

    60 KiB could be saved by minifying JavaScript.

  • Main-thread work: 3.7 s

    A phone's processor spends 3.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Listrak adds 217 ms

    217 ms

    Listrak costs a phone 217 ms of main-thread work and 610 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.

  • 12 long tasks on the main thread

    12 long tasks block the main thread while loading, the longest for 272 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    150 ms · 9 KiB

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

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

  • Forced reflow

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

14 to fix33
  • 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.

  • First Contentful Paint: 24.5 s

    24.5 s

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

  • Largest Contentful Paint: 37.0 s

    37.0 s

    Your largest element takes 37.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Guide Halloween Creativity Discover spooky crafts, coloring…”.

  • Speed Index: 24.5 s

    24.5 s

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

  • Time to Interactive: 39.2 s

    39.2 s

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

  • Cumulative Layout Shift: 1.114

    1.114

    The layout shifts by 1.114 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user CLS: 0.18

    0.18

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 120 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 122% slower for real visitors

    +122%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 960 ms

    960 ms

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

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

  • Total Blocking Time: 203 ms

    203 ms

    Scripts block taps and scrolling for 203 ms in total while the page loads. Good is under 200 ms.

1 checks passed
  • Real-user INP: 161 ms

    161 ms

    Real visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Images and page weight

5 to fix33
  • Page weight: 7.7 MB in 134 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 134 requests on a phone: images 2.7 MB (46), scripts 2.4 MB (40) and stylesheets 2.0 MB (9). Under 2 MB keeps phones on slow connections fast.

  • 8 images far larger than shown

    608 KiB

    8 images are downloaded at several times the size a phone draws them, for example crayola-adult-colouring-link.jpg at 563 px wide, shown at 105 px. Resized copies would save about 608 KiB.

  • 20 images in older formats

    20 images (1.5 MB) are 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.

  • An image on the first screen is lazy-loaded

    hero-hauntedhouse.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).

  • 10 images below the first screen load straight away

    10 images further down the page (955 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.20 g

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

Accessibility

6 to fixGoogle 8992
  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate 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.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

1 checks passed
  • 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. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • 15 links with vague text

    15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 224 internal links, 9 external

    The homepage links to 224 pages on crayola.com and 9 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Explore Crayola art supplies, kids' toys, free coloring pages, DIY crafts, creative prompts, and educational resources …”.

  • One H1 headline

    Your main headline reads: “Halloween Creativity”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Home | Products, Coloring Pages, Crafts & More”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.crayola.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 (1,482 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.crayola.com/products and https://www.crayola.com/menu/products/product-types all use the title “Shop All Crayola Art Supplies, Toys & Classpacks”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://www.crayola.com/menu/products/product-types, whose canonical is https://www.crayola.com/products. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages share a meta description

    https://www.crayola.com/products and https://www.crayola.com/menu/products/product-types use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 134 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

4 to fixGoogle 5483
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Unrecognized Content-Security-Policy directive 'video-src'.”.

  • 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

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 738 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Learn More”, “Where to Buy” and “Contact Us”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).

  • 32 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 crayola.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on crayola.com, including 27 speed issues, 3 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