Programmable

Website review, no card needed

otovo.com logo

otovo.com website review

Visit site (opens in a new tab)Reviewed 31 October 202612 issues · 75 checks

This review found 12 issues worth fixing on otovo.com, 3 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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

Site score

92A

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.6 s2.0 sJul 4Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
Jul 4, 20263.2 s
Jul 11, 20263.4 s
Jul 18, 20263.1 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.5 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
181 ms94 msJul 18Oct 24104 ms
Show as table
DateReal-visitor tap response (INP)
Jul 18, 2026162 ms
Jul 25, 2026171 ms
Aug 1, 2026166 ms
Aug 8, 2026146 ms
Aug 15, 2026129 ms
Aug 22, 2026112 ms
Aug 29, 2026122 ms
Sep 5, 2026128 ms
Sep 12, 2026127 ms
Sep 19, 2026127 ms
Sep 26, 2026128 ms
Oct 3, 2026121 ms
Oct 10, 2026119 ms
Oct 17, 2026110 ms
Oct 24, 2026104 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

otovo.com (opens in a new tab)
Full-page screenshot of otovo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix81

  • Render-blocking requests

    1.4 s

    21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Mobile performance score: 81

    81/100

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

  • Improve image delivery

    450 ms · 181 KiB

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

  • Reduce unused JavaScript

    150 ms · 25 KiB

    About 25 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 13 KiB

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

  • 1 long task on the main thread

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

  • Use efficient cache lifetimes

    36 KiB

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

  • Legacy JavaScript

    10 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 12 KiB and 6 ms of main-thread time.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed

  • Main-thread work: 0.7 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

2 to fix100

  • Largest Contentful Paint: 5.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Multi-generational family enjoying their solar-powered home”.

  • Time to Interactive: 5.1 s

    5.1 s

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

12 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.9 s

    1.9 s

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

  • Real-user INP: 126 ms

    126 ms

    Real visitors wait 126 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.7 s

    1.7 s

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

  • Real-user TTFB: 759 ms

    759 ms

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

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

    -36%

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

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

    -28%

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

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 13 ms

    13 ms

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

Images and page weight

100

  • About 0.2 g of CO₂ per visit

    0.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.22 g of CO₂e: 26.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed

  • Page weight: 797 KiB in 221 requests

    797 KiB

    Your homepage downloads 797 KiB in 221 requests on a phone: scripts 382 KiB (168), images 247 KiB (19) and stylesheets 83 KiB (24). That is a lean page.

  • 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

3 to fixGoogle 9597

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

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

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed

  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095

  • 2 H1 headlines

    There are 2 <h1> headlines (“POWER. PROTECTED.” and “POWER. PROTECTED.”). One clear main headline is easier for people and search engines.

  • 55 internal links, 34 external

    The homepage links to 55 pages on otovo.com and 34 external pages.

7 checks passed

  • Meta description: 113 characters

    Your meta description is 113 characters: “Hardware monitoring, software intelligence, and human expertise all in one service. The only membership you need.”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Otovo - Solar, Battery, Generator and EV Charger Service”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (630 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://otovo.com/privacy-policy, whose canonical is https://otovo.com/legal/privacy-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

6 checks passed

  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Every page has a meta description

    All 14 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79

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

  • Thin social proof

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

  • About 414 words of copy

    The homepage carries about 414 words of visible text.

5 checks passed

  • 7 calls to action

    The homepage has 7 calls to action, for example “Job Opportunities Join the team”, “Contact” and “Book a Repair”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 otovo.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
SvelteKit
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 12 issues on otovo.com, including 5 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

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