Website review, no card needed

lovespotbg.com logo

lovespotbg.com website review

Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 71 checks

This review found 30 issues worth fixing on lovespotbg.com, 10 of them high impact, across 71 checks. The most urgent: 14 pages without a title. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of lovespotbg.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lovespotbg.com at 0.6 s0.6 s
  2. lovespotbg.com at 1.2 s1.2 s
  3. lovespotbg.com at 1.8 s1.8 s
  4. lovespotbg.com at 2.5 s2.5 s
  5. lovespotbg.com at 3.1 s3.1 s
  6. lovespotbg.com at 3.7 s3.7 s
  7. lovespotbg.com at 4.3 s4.3 s
  8. lovespotbg.com at 4.9 s4.9 s

Speed

4 to fix95
  • Render-blocking requests

    750 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Use efficient cache lifetimes

    302 KiB

    12 files are served with short cache lifetimes, so returning visitors download them again (302 KiB).

  • Reduce unused JavaScript

    288 KiB

    About 288 KiB of JavaScript is downloaded but never used on this page.

  • Shopify adds 145 ms

    145 ms

    Shopify costs a phone 145 ms of main-thread work and 469 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 (Shopify, Facebook and Cloudflare CDN and others), adding 942 KiB and 342 ms of main-thread time.

  • Improve image delivery

    50 ms · 109 KiB

    7 images could be 109 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    12 KiB

    About 12 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.

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 553 ms of it running JavaScript. That is comfortably low.

  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix95
  • Time to Interactive: 10.7 s

    10.7 s

    The page becomes fully interactive after 10.7 s. Good is under 3.8 s.

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your 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 image.

  • Speed Index: 3.7 s

    3.7 s

    Visually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.

  • 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
  • Cumulative Layout Shift: 0.049

    0.049

    The layout barely moves while loading (CLS 0.049, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 29 ms

    29 ms

    Scripts block the page for only 29 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 209 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 209 requests on a phone: scripts 931 KiB (56), other files 847 KiB (113) and images 220 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.60 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 72.2 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

5 to fixGoogle 9294
  • 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.

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8366
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • One H1 headline

    Your <h1> is empty.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 40 internal links, 6 external

    The homepage links to 40 pages on lovespotbg.com and 6 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://lovespotbg.com/.

  • 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://lovespotbg.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

    The site publishes https://lovespotbg.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix71
  • 14 pages without a title

    https://lovespotbg.com/products/love-map, https://lovespotbg.com/products/%D0%BF%D0%BE%D0%B4%D0%B0%D1%80%D1%8A%D0%BA-%D1%84%D0%B8%D0%BB%D0%BC%D0%BE%D0%B2-%D0%BF%D0%BE%D1%81%D1%82%D0%B5%D1%80-%D0%B7%D0%B0-%D0%B4%D0%B2%D0%BE%D0%B9%D0%BA%D0%B8, https://lovespotbg.com/products/%D0%BF%D0%BE%D0%B4%D0%B0%D1%80%D1%8A%D0%BA-%D0%B7%D0%B0-8-%D0%BC%D0%B0%D1%80%D1%82-%D0%BC%D0%B0%D0%B9%D0%BA%D0%B0, https://lovespotbg.com/products/%D0%B7%D0%B2%D0%B5%D0%B7%D0%B4%D0%B5%D0%BD-%D1%81%D0%BF%D0%BE%D0%BC%D0%B5%D0%BD, https://lovespotbg.com/pages/contact and https://lovespotbg.com/collections/%D0%BF%D0%BB%D0%BE%D0%B4%D0%BE%D0%B2%D0%B8-%D0%BF%D0%BE%D1%81%D1%82%D0%B5%D1%80%D0%B8 and 8 others have no <title>, so Google invents the link text in results.

  • 14 pages without a meta description

    https://lovespotbg.com/products/love-map, https://lovespotbg.com/products/%D0%BF%D0%BE%D0%B4%D0%B0%D1%80%D1%8A%D0%BA-%D1%84%D0%B8%D0%BB%D0%BC%D0%BE%D0%B2-%D0%BF%D0%BE%D1%81%D1%82%D0%B5%D1%80-%D0%B7%D0%B0-%D0%B4%D0%B2%D0%BE%D0%B9%D0%BA%D0%B8, https://lovespotbg.com/products/%D0%BF%D0%BE%D0%B4%D0%B0%D1%80%D1%8A%D0%BA-%D0%B7%D0%B0-8-%D0%BC%D0%B0%D1%80%D1%82-%D0%BC%D0%B0%D0%B9%D0%BA%D0%B0, https://lovespotbg.com/products/%D0%B7%D0%B2%D0%B5%D0%B7%D0%B4%D0%B5%D0%BD-%D1%81%D0%BF%D0%BE%D0%BC%D0%B5%D0%BD, https://lovespotbg.com/pages/contact and https://lovespotbg.com/collections/%D0%BF%D0%BB%D0%BE%D0%B4%D0%BE%D0%B2%D0%B8-%D0%BF%D0%BE%D1%81%D1%82%D0%B5%D1%80%D0%B8 and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 links to non-canonical URLs

    Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://lovespotbg.com/products/%D0%BF%D0%BE%D0%B4%D0%B0%D1%80%D1%8A%D0%BA-%D1%84%D0%B8%D0%BB%D0%BC%D0%BE%D0%B2-%D0%BF%D0%BE%D1%81%D1%82%D0%B5%D1%80-%D0%B7%D0%B0-%D0%B4%D0%B2%D0%BE%D0%B9%D0%BA%D0%B8, whose canonical is https://lovespotbg.com/products/%d0%bf%d0%be%d0%b4%d0%b0%d1%80%d1%8a%d0%ba-%d1%84%d0%b8%d0%bb%d0%bc%d0%be%d0%b2-%d0%bf%d0%be%d1%81%d1%82%d0%b5%d1%80-%d0%b7%d0%b0-%d0%b4%d0%b2%d0%be%d0%b9%d0%ba%d0%b8. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 pages with very little text

    https://lovespotbg.com/products/love-map, https://lovespotbg.com/products/%D0%BF%D0%BE%D0%B4%D0%B0%D1%80%D1%8A%D0%BA-%D1%84%D0%B8%D0%BB%D0%BC%D0%BE%D0%B2-%D0%BF%D0%BE%D1%81%D1%82%D0%B5%D1%80-%D0%B7%D0%B0-%D0%B4%D0%B2%D0%BE%D0%B9%D0%BA%D0%B8, https://lovespotbg.com/products/%D0%BF%D0%BE%D0%B4%D0%B0%D1%80%D1%8A%D0%BA-%D0%B7%D0%B0-8-%D0%BC%D0%B0%D1%80%D1%82-%D0%BC%D0%B0%D0%B9%D0%BA%D0%B0, https://lovespotbg.com/products/%D0%B7%D0%B2%D0%B5%D0%B7%D0%B4%D0%B5%D0%BD-%D1%81%D0%BF%D0%BE%D0%BC%D0%B5%D0%BD, https://lovespotbg.com/pages/contact and https://lovespotbg.com/collections/%D0%BF%D0%BB%D0%BE%D0%B4%D0%BE%D0%B2%D0%B8-%D0%BF%D0%BE%D1%81%D1%82%D0%B5%D1%80%D0%B8 and 8 others 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 and read each the way a search engine does.

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 10078
  • 2 broken images

    2 images failed to load on a phone, for example https://lovespotbg.com/.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://scoutefy.com/css/scout.css?id=dc8fb27b6acf0e571743' from origin 'https://lovespotb…”.

2 checks passed
  • Tap targets are thumb-sized

    9 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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.

  • 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 62 words

    The homepage has only about 62 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.

1 checks passed
  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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

    9

    Opening 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.

  • 19 other companies contacted

    Loading the homepage contacts 19 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 lovespotbg.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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Reelup Shoppable Videos Reels · Judge Me Reviews · Releasit Cod Form · Ymq Product Options · Adscout · B S Announcements · Scarcity Ai Timers · Shpf Bar · nfcube.com · rushyapp.com

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

E-commerce
Shopify
Hosting
Shopify

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 lovespotbg.com, including 7 speed issues, 4 SEO issues and 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25