Website review, no card needed
seven-retail.com website review
Visit site (opens in a new tab)Reviewed 31 October 202625 issues · 65 checks
This review found 25 issues worth fixing on seven-retail.com, 13 of them high impact, across 65 checks. The most urgent: use efficient cache lifetimes. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.3 s |
| Oct 24, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 125 ms |
| May 16, 2026 | 123 ms |
| May 23, 2026 | 127 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 115 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 128 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 124 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 114 ms |
| Oct 24, 2026 | 117 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.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Use efficient cache lifetimes
3.5 s · 1.0 MB9 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Improve image delivery
3.5 s · 1,005 KiB2 images could be 1,005 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.
Render-blocking requests
1.1 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
1 third-party service on the page
1 third-party service load with your homepage (cloudfront.net), adding 1.0 MB and 0 ms of main-thread time.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 1.0 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 154 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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, 290 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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.
Real-user CLS: 0.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero”. Most of its time is resource load delay (4.5 s).
Cumulative Layout Shift: 0.368
0.368The layout shifts by 0.368 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 125 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 113 ms
113 msReal visitors wait 113 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 777 ms
777 msReal visitors wait 777 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 42.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.3 MB in 36 requests
1.3 MBYour homepage downloads 1.3 MB in 36 requests on a phone: images 1.0 MB (9), scripts 114 KiB (8) and fonts 98 KiB (8). That is a lean page.
Accessibility
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.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 1 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
7 internal links, 0 external
The homepage links to 7 pages on seven-retail.com and 0 external pages.
4 checks passed
Meta description: 120 characters
Your meta description is 120 characters: “Welcome to Seven Retail. Explore our values, discover our brands, and learn about exciting career opportunities with us.”.
Title: 37 characters
Your title is a healthy 37 characters: “Welcome to Our Company - Seven Retail”.
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://seven-retail.com/sitemap.xml.
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://seven-retail.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.
1 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.
Other pages
4 pages without an H1
https://seven-retail.com/brands, https://seven-retail.com/career, https://seven-retail.com/contact and https://seven-retail.com/about have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://seven-retail.com/brands, https://seven-retail.com/career, https://seven-retail.com/contact and https://seven-retail.com/about 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.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 4 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 4 pages that loaded have a meta description.
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 4 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://seven-retail.com/.
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
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 11 words
The homepage has only about 11 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 seven-retail.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
- Next.js
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on seven-retail.com, including 13 speed issues, 4 SEO issues and 4 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.