Website review, no card needed
redapplefireworks.com website review
Visit site (opens in a new tab)Reviewed 6 November 202629 issues · 80 checks
This review found 29 issues worth fixing on redapplefireworks.com, 10 of them high impact, across 80 checks. The most urgent: page weight: 9.7 MB in 107 requests. 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
87B- #8,157 of 117,615 reviewed websitesbeats 90%
- #4,752 of 66,923 online storesbeats 89%
- #4,611 of 61,018 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 968 ms |
| May 23, 2026 | 962 ms |
| May 30, 2026 | 938 ms |
| Jun 6, 2026 | 912 ms |
| Jun 13, 2026 | 911 ms |
| Jun 20, 2026 | 913 ms |
| Jun 27, 2026 | 924 ms |
| Jul 4, 2026 | 951 ms |
| Jul 11, 2026 | 911 ms |
| Jul 18, 2026 | 907 ms |
| Jul 25, 2026 | 897 ms |
| Aug 1, 2026 | 846 ms |
| Aug 8, 2026 | 926 ms |
| Aug 15, 2026 | 970 ms |
| Aug 22, 2026 | 987 ms |
| Aug 29, 2026 | 995 ms |
| Sep 5, 2026 | 998 ms |
| Sep 12, 2026 | 968 ms |
| Sep 19, 2026 | 905 ms |
| Sep 26, 2026 | 829 ms |
| Oct 3, 2026 | 800 ms |
| Oct 10, 2026 | 847 ms |
| Oct 17, 2026 | 922 ms |
| Oct 24, 2026 | 969 ms |
| Oct 31, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 146 ms |
| May 23, 2026 | 153 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 154 ms |
| Jun 27, 2026 | 158 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 148 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 174 ms |
| Aug 15, 2026 | 179 ms |
| Aug 22, 2026 | 179 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 178 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 179 ms |
| Oct 24, 2026 | 173 ms |
| Oct 31, 2026 | 171 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
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
5,547 HTML elements
The page has 5,547 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 482 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 18 ms
18 msShopify costs a phone 18 ms of main-thread work and 441 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 (Google Tag Manager, tncapp.com and Shopify and others), adding 813 KiB and 286 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 199 ms. During a long task the page ignores taps.
Reduce unused JavaScript
155 KiBAbout 155 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
55 KiBAbout 55 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
49 KiB5 files are served with short cache lifetimes, so returning visitors download them again (49 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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 7.8 s
7.8 sThe page becomes fully interactive after 7.8 s. Good is under 3.8 s.
Real-user INP: 269 ms
269 msReal visitors wait 269 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 273 ms
273 msScripts block taps and scrolling for 273 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 697 ms
697 msReal visitors wait 697 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.074
0.074The layout barely moves while loading (CLS 0.074, good is under 0.1).
Largest Contentful Paint: 1.9 s
1.9 sYour largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the element shown below.
Images and page weight
Page weight: 9.7 MB in 107 requests
9.7 MBYour homepage downloads 9.7 MB in 107 requests on a phone: media 5.6 MB (4), images 2.9 MB (22) and scripts 858 KiB (58). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.
11 images in older formats
11 images (2.9 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
Countdown_to_4th_of_July_home_page_banner-Mobile-1200x1600_1 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.7 g of CO₂ per visit
2.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.75 g of CO₂e: 329.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
4 images without alt text
4 images have 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
381 internal links, 19 external
The homepage links to 381 pages on redapplefireworks.com and 19 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Light up the sky with Red Apple® Fireworks! Shop our massive selection of aerials, mortars & cakes online 🎆 Get big bu…”.
One H1 headline
Your main headline reads: “Premium Fireworks - Extensive Selection & Unmatched Quality”.
Title: 59 characters
Your title is a healthy 59 characters: “Buy Fireworks Online | Premium Red Apple® Products for Sale”.
Canonical URL set
The canonical URL is https://www.redapplefireworks.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, 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://www.redapplefireworks.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 3 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
Opted out of AI training for 1 crawler
robots.txt blocks Applebot-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (3,635 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.redapplefireworks.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.redapplefireworks.com/products/club-red-apple-membership has no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.redapplefireworks.com/collections/finale-sets, https://www.redapplefireworks.com/collections/reloadable-shell-kits, https://www.redapplefireworks.com/collections/aerial-cakes, https://www.redapplefireworks.com/collections/roman-candles, https://www.redapplefireworks.com/collections/rockets and https://www.redapplefireworks.com/collections/missiles and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.redapplefireworks.com/collections/preloaded-shells, https://www.redapplefireworks.com/collections/sky-spinners and https://www.redapplefireworks.com/collections/firing-system have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 132 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.
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 15 pages that loaded have a <title>.
Best practices
36 small tap targets
36 of 85 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'start')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 65 testimonial or review blocks. 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.
About 2,533 words of copy
The homepage carries about 2,533 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN THE CLUB →” and “SHOP BY FIREWORK Shop Now”.
44 calls to action
The homepage has 44 calls to action, for example “SHOP NOW!”, “JOIN NOW” and “SHOP NOW”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
8 other companies contacted
Loading the homepage contacts 8 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 redapplefireworks.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 22 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Sitemap Noindex Pro Seo · Judge Me Reviews · Helium Customer Fields · Smart Seo · Tnc Terms Checkbox · Crisp Live Chat Chatbot · Zapiet Pickup Delivery · Sendlane Marketing Automation · Microsoft Clarity · Optimonk Popup Cro A B Test · Specification And Compare · Accessibly App · Countdown Timer · Crisp Chatbox · Swish Wishlist King · Estimated Delivery Days · Sidekick · Essential Pre Order Presale · Xo Scroll To Top · verifypass.com · herokuapp.com · socialsnowball.io
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on redapplefireworks.com, including 9 speed 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.