Website review, no card needed
spon.com website review
Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 69 checks
This review found 30 issues worth fixing on spon.com, 6 of them high impact, across 69 checks. The most urgent: page weight: 36.7 MB in 43 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
77CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.6 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
5 third-party services on the page
5 third-party services load with your homepage (website-files.com, Cloudflare CDN and JSDelivr CDN and others), adding 36.6 MB and 258 ms of main-thread time.
Vimeo adds 0 ms
0 msVimeo costs a phone 0 ms of main-thread work and 33.2 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.
Use efficient cache lifetimes
600 ms · 2.6 MB8 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 124 KiBAbout 124 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
website-files.com adds 111 ms
111 mswebsite-files.com costs a phone 111 ms of main-thread work and 3.2 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.
Improve image delivery
66 KiB3 images could be 66 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
17 KiBAbout 17 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: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 310 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
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 5.7 s
5.7 sThe page becomes fully interactive after 5.7 s. Good is under 3.8 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
2 images without width and height
2 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.
3 checks passed
Speed Index: 2.3 s
2.3 sVisually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
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
Page weight: 36.7 MB in 43 requests
36.7 MBYour homepage downloads 36.7 MB in 43 requests on a phone: media 35.7 MB (11), fonts 388 KiB (3) and scripts 285 KiB (12). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
66ec526522a1df9ec44dd9f6_JP_Damboragian_SunBum_Good_Days_Dai 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 10.4 g of CO₂ per visit
10.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.39 g of CO₂e: 1246.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 1 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (4 characters)
Your title is only 4 characters: “LVLY”. 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.
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 XML sitemap
No XML sitemap at https://www.lvly.tv/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
18 internal links, 8 external
The homepage links to 18 pages on spon.com and 8 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
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://www.lvly.tv/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
7 pages share a title
/, https://www.lvly.tv/work/amazon-fall-launch, https://www.lvly.tv/work/reverse, https://www.lvly.tv/editorial/olivier-wicki, https://www.lvly.tv/work/amazon-alexa-super-bowl and https://www.lvly.tv/work/good-days-daily and 1 other all use the title “LVLY”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://www.lvly.tv/design, https://www.lvly.tv/about, https://www.lvly.tv/contact, https://www.lvly.tv/editorial, https://www.lvly.tv/cg-vfx and https://www.lvly.tv/beauty and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.lvly.tv/contact has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.lvly.tv/contact has 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.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 13 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 13 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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 69 words
The homepage has only about 69 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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: “Contact”.
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Join Us”.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 spon.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Hosting
- Cloudflare
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on spon.com, including 11 speed issues, 7 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.