Website review, no card needed

sondors.com logo

sondors.com website review

Visit site (opens in a new tab)Reviewed 9 November 202624 issues · 54 checks

This review found 24 issues worth fixing on sondors.com, 8 of them high impact, across 54 checks. The most urgent: no call to action on the first screen. 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

Real-visitor load time (LCP)75th percentile, phones
2.5 s916 msMay 23Nov 71.3 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.3 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.1 s
Sep 5, 20261.8 s
Sep 12, 20261.5 s
Sep 19, 20261.3 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
97 ms39 msMay 23Nov 778 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202690 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202686 ms
Aug 8, 202687 ms
Aug 15, 202686 ms
Aug 22, 202686 ms
Aug 29, 202687 ms
Sep 5, 202685 ms
Sep 12, 202680 ms
Sep 19, 202670 ms
Sep 26, 202654 ms
Oct 3, 202646 ms
Oct 10, 202646 ms
Oct 17, 202648 ms
Oct 24, 202656 ms
Oct 31, 202662 ms
Nov 7, 202678 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

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

How it loaded on a phone

  1. sondors.com at 0.4 s0.4 s
  2. sondors.com at 0.8 s0.8 s
  3. sondors.com at 1.1 s1.1 s
  4. sondors.com at 1.5 s1.5 s
  5. sondors.com at 1.9 s1.9 s
  6. sondors.com at 2.3 s2.3 s
  7. sondors.com at 2.6 s2.6 s
  8. sondors.com at 3.0 s3.0 s

Speed

3 to fix60
  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

  • Reduce unused JavaScript

    450 ms · 74 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 214 KiB and 129 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.

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

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

  • Server response: 116 ms

    116 ms

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

Core Web Vitals

4 to fix100
  • First Contentful Paint: 6.2 s

    6.2 s

    The first text or image appears after 6.2 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “i asked for gas. not a fucking engagement ring. SONDORS 001”.

  • Speed Index: 6.2 s

    6.2 s

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

  • Time to Interactive: 7.8 s

    7.8 s

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

10 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: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 78 ms

    78 ms

    Real visitors wait 78 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 745 ms

    745 ms

    Real visitors wait 745 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 21% faster for real visitors

    -21%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 90 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 43% faster for real visitors

    -43%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 38 ms

    38 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.31 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.31 g of CO₂e: 36.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.1 MB in 6 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 6 requests on a phone: HTML 884 KiB (1), scripts 182 KiB (2) and fonts 35 KiB (1). That is a lean page.

Accessibility

1 to fixGoogle 10098
  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

9 to fixGoogle 9153
  • 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 (3 characters)

    Your title is only 3 characters: “001”. 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 XML sitemap

    No XML sitemap at https://sondors.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at sondors.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 checks passed
  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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.

  • No llms.txt

    There is no https://sondors.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 4 words

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

3 checks passed
  • 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 Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 sondors.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
Analytics
Google Analytics
Hosting
Netlify

Company

Headquarters
Malibu

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on sondors.com, including 7 speed issues, 9 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

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