Website review, no card needed
launchingdeals.com website review
Visit site (opens in a new tab)Reviewed 5 November 202633 issues · 71 checks
This review found 33 issues worth fixing on launchingdeals.com, 12 of them high impact, across 71 checks. The most urgent: render-blocking 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
85B- #16,662 of 124,235 reviewed websitesbeats 82%
- #10,479 of 69,824 online storesbeats 80%
- #10,173 of 63,496 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 87 ms |
| May 23, 2026 | 85 ms |
| May 30, 2026 | 85 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 88 ms |
| Jul 4, 2026 | 92 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 89 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 89 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 89 ms |
| Aug 29, 2026 | 89 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 88 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 88 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 87 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.2 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Use efficient cache lifetimes
1.3 MB30 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Improve image delivery
1.3 MB21 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 84
84/100Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 125 KiBAbout 125 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Riskified and Shopify and others), adding 1.6 MB and 153 ms of main-thread time.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 ms of main-thread work and 1.3 MB 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
Reduce unused CSS
36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page.
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.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 349 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 9.0 s
9.0 sVisually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.0 s
8.0 sThe page becomes fully interactive after 8.0 s. Good is under 3.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.7 s
2.7 sYour largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Save on Shopping & More”. Most of its time is element render delay (2.5 s).
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 87 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 243 ms
243 msReal visitors wait 243 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
10 images far larger than shown
1.1 MB10 images are downloaded at several times the size a phone draws them, for example T-Mobile.png at 2,132 px wide, shown at 186 px. Resized copies would save about 1.1 MB.
Page weight: 2.8 MB in 145 requests
2.8 MBYour homepage downloads 2.8 MB in 145 requests on a phone: images 1.6 MB (33), other files 616 KiB (66) and scripts 461 KiB (34). Under 2 MB keeps phones on slow connections fast.
10 images in older formats
10 images (1.1 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.
12 images below the first screen load straight away
12 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is short (15 characters)
Your title is only 15 characters: “Launching Deals”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
7 internal links, 0 external
The homepage links to 7 pages on launchingdeals.com and 0 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Save on Shopping & More”.
Canonical URL set
The canonical URL is https://launchingdeals.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://launchingdeals.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
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://launchingdeals.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (203 words), so crawlers that don't run JavaScript still read it.
Other pages
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
1 checks passed
Linked pages load
1 page of 4 loaded without an error (the rest turned automated requests away).
Best practices
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 22 customer or partner logos. 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.
Only about 152 words
The homepage has only about 152 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get Started”.
4 calls to action
The homepage has 4 calls to action, for example “Join Today”, “Get Started” and “Contact Us”.
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
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.
9 cookies set on arrival
9Opening 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.
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.
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 launchingdeals.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- 10 Shopify Products;Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on launchingdeals.com, including 12 speed issues, 5 SEO issues and 3 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.