Website review, no card needed
redlinesociety.com website review
Visit site (opens in a new tab)Reviewed 8 November 202628 issues · 99 checks
This review found 28 issues worth fixing on redlinesociety.com, 8 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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
81B- #26,470 of 81,205 reviewed websitesbeats 62%
- #15,736 of 40,119 online storesbeats 54%
- #14,996 of 35,509 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 162 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 187 ms |
| Jun 20, 2026 | 200 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 202 ms |
| Jul 18, 2026 | 199 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 208 ms |
| Aug 8, 2026 | 212 ms |
| Aug 15, 2026 | 213 ms |
| Aug 22, 2026 | 225 ms |
| Aug 29, 2026 | 231 ms |
| Sep 5, 2026 | 237 ms |
| Sep 12, 2026 | 234 ms |
| Sep 19, 2026 | 227 ms |
| Sep 26, 2026 | 229 ms |
| Oct 3, 2026 | 239 ms |
| Oct 10, 2026 | 254 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 246 ms |
| Oct 31, 2026 | 239 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
4.4 s
8.7 s
13.1 s
17.5 s
21.8 s
26.2 s
30.6 s
34.9 s
redlinesociety.com does not allow embedding, so this is Google's rendering of the page.
Speed
Reduce unused JavaScript
1.1 s · 785 KiBAbout 785 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.6 MB and 1.4 s of main-thread time.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Google Tag Manager adds 429 ms
429 msGoogle Tag Manager costs a phone 429 ms of main-thread work and 517 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.
Use efficient cache lifetimes
437 KiB14 files are served with short cache lifetimes, so returning visitors download them again (437 KiB).
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 303 ms
303 msFacebook costs a phone 303 ms of main-thread work and 311 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.
Klaviyo adds 179 ms
179 msKlaviyo costs a phone 179 ms of main-thread work and 505 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.
Legacy JavaScript
150 ms · 100 KiBPolyfills for old browsers add 100 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 49 KiBAbout 49 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 198 ms. During a long task the page ignores taps.
Improve image delivery
58 KiB4 images could be 58 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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: 19.6 s
19.6 sThe page becomes fully interactive after 19.6 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The black RS61 twin turbo F-150 with red beadlock wheels”.
Total Blocking Time: 756 ms
756 msScripts block taps and scrolling for 756 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 220 ms
220 msReal visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 162 ms to 239 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 567 ms
567 msReal visitors wait 567 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.5 s
2.5 sVisually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.0 MB in 195 requests
3.0 MBYour homepage downloads 3.0 MB in 195 requests on a phone: scripts 2.3 MB (95), fonts 384 KiB (18) and images 143 KiB (9). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 103.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Redline Society”. Between 30 and 65 characters leaves room to say what you do and for whom.
61 internal links, 6 external
The homepage links to 61 pages on redlinesociety.com and 6 external pages.
7 checks passed
Meta description: 113 characters
Your meta description is 113 characters: “Dream car giveaways and limited apparel drops. Every order earns entries. Every drawing published and verifiable.”.
One H1 headline
Your main headline reads: “Your driveway.1,100 morehorsepower.”.
Canonical URL set
The canonical URL is https://redlinesociety.com/.
Structured data in place
Structured data found: Organization.
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://redlinesociety.com/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no /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, which the crawlers above handle.
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 (868 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
/free-play is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343198878&tm=gtm002&Ver=2&mid=de9392c9-ee0c-40d2-b403-cfa4948081b7&bo=1&sid=2f6483e0dba211f1a743f5f9847eea0d&vid=2f649b90dba211f1b6f333c418a0c7cc&vids=1&msclkid=N&pi=9.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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.
Security and trust
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
8 checks passed
Served over HTTPS
The homepage is served over HTTPS (redlinesociety.com).
Valid certificate (31 days left)
The certificate from Let's Encrypt · YE2 verifies for redlinesociety.com and is valid for another 31 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://redlinesociety.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 43 links work
All 43 links checked from your homepage (40 internal, 3 external) answered without errors.
Domain and trust
No CAA record
redlinesociety.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
redlinesociety.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 12 years old
12 yearsredlinesociety.com was registered in Dec 2013 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Registered until Dec 2033
redlinesociety.com is registered until Dec 2033.
Content and conversion
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 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 659 words of copy
The homepage carries about 659 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: “Search giveaways and shop”.
9 calls to action
The homepage has 9 calls to action, for example “Shop”, “Search giveaways and shop” and “DEMO REVEALNO PRIZE AWARDEDSpin again ↻”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be redlinesociety.com is still delivered. Add a report address, check the reports, then move to quarantine.
Email authentication score: 70/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 ip4:168.245.13.102 ip4:149.72.191.132 include:emsd1.com include:shops.shopify.com include:sendgrid.net include:_…”.
DKIM signing found
A DKIM key is published (selector “google”), so receivers can verify mail really came from you.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
29 other companies contacted
Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- Framework
- Next.js
- E-commerce
- Shopify;Shopify Plus
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on redlinesociety.com, including 16 speed issues, 1 SEO issue 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.