Website review, no card needed
dayglo.com website review
Visit site (opens in a new tab)Reviewed 24 October 202635 issues · 79 checks
This review found 35 issues worth fixing on dayglo.com, 17 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
77CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
44.4 s · 9.8 MB11 images could be 9.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 44.4 s faster on a phone.
Render-blocking requests
3.6 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Reduce unused CSS
1.8 s · 327 KiBAbout 327 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Reduce unused JavaScript
1.6 s · 307 KiBAbout 307 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 257 KiB13 files are served with short cache lifetimes, so returning visitors download them again (257 KiB).
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
400 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
1,728 HTML elements
The page has 1,728 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (Facebook, Optanon and Cloudflare CDN and others), adding 893 KiB and 343 ms of main-thread time.
Document request latency
141 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 76 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 85 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
6 KiB6 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 453 ms of it running JavaScript. That is comfortably low.
Server response: 82 ms
82 msYour server sent the HTML in 82 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 56.6 s
56.6 sYour largest element takes 56.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Get Your Product Noticed With Dayglo Aurora Pink”.
Time to Interactive: 56.6 s
56.6 sThe page becomes fully interactive after 56.6 s. Good is under 3.8 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
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.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Total Blocking Time: 33 ms
33 msScripts block the page for only 33 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 11.5 MB in 83 requests
11.5 MBYour homepage downloads 11.5 MB in 83 requests on a phone: images 10.0 MB (26), scripts 817 KiB (24) and stylesheets 347 KiB (12). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
get-your-product-noticed-with-dayglo-saturn-yellow.png weighs 7.6 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
6.9 MB1 image is downloaded at several times the size a phone draws it, for example get-your-product-noticed-with-dayglo-saturn-yellow.png at 3,594 px wide, shown at 372 px. Resized copies would save about 6.9 MB.
9 images in older formats
9 images (9.7 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.
2 images below the first screen load straight away
2 images further down the page (645 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.3 g of CO₂ per visit
3.27 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.27 g of CO₂e: 392.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (30 elements)
All page content should be contained by landmarks: 30 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h6 and h3 → h6), 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. (1 element).
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Improve Product Visibility!”, “Markets we operate in” and “Product Types”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
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.
361 internal links, 104 external
The homepage links to 361 pages on dayglo.com and 104 external pages.
4 checks passed
Title: 55 characters
Your title is a healthy 55 characters: “DayGlo Color Corp | Daylight Fluorescent Pigment Leader”.
Canonical URL set
The canonical URL is https://www.dayglo.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.dayglo.com/sitemap/.
AI search readiness
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://dayglo.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,210 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages share 2 titles
https://dayglo.com/blog and https://dayglo.com/products/all-products all use the title “DayGlo”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://dayglo.com/blog, https://dayglo.com/products, https://dayglo.com/products/all-products, https://dayglo.com/products/fluorescent-pigments, https://dayglo.com/products/fluorescent-toners and https://dayglo.com/products/fluorescent-dispersions and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://dayglo.com/blog and https://dayglo.com/markets 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 37 found) and read each the way a search engine does.
4 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.
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
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
13 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 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.
About 349 words of copy
The homepage carries about 349 words of visible text.
3 checks passed
14 calls to action
The homepage has 14 calls to action, for example “Shop Direct”, “Contact” and “The Power of Color - Learn More”.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Meta Pixel (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.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
11 other companies contacted
Loading the homepage contacts 11 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 dayglo.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 35 issues on dayglo.com, including 13 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.