Website review, no card needed

otter.ro logo

otter.ro website review

Visit site (opens in a new tab)Reviewed 20 October 202637 issues · 83 checks

This review found 37 issues worth fixing on otter.ro, 15 of them high impact, across 83 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

Real-visitor load time (LCP)75th percentile, phones
3.9 s2.3 sMay 2Oct 172.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.2 s
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.3 s
Sep 26, 20262.9 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
500 ms188 msMay 2Oct 17307 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026231 ms
May 9, 2026228 ms
May 16, 2026225 ms
May 23, 2026224 ms
May 30, 2026227 ms
Jun 6, 2026232 ms
Jun 13, 2026242 ms
Jun 20, 2026260 ms
Jun 27, 2026279 ms
Jul 4, 2026299 ms
Jul 11, 2026315 ms
Jul 18, 2026322 ms
Jul 25, 2026327 ms
Aug 1, 2026333 ms
Aug 8, 2026346 ms
Aug 15, 2026349 ms
Aug 22, 2026355 ms
Aug 29, 2026354 ms
Sep 5, 2026355 ms
Sep 12, 2026378 ms
Sep 19, 2026402 ms
Sep 26, 2026444 ms
Oct 3, 2026464 ms
Oct 10, 2026406 ms
Oct 17, 2026307 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 otter.ro (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. otter.ro at 0.9 s0.9 s
  2. otter.ro at 1.8 s1.8 s
  3. otter.ro at 2.7 s2.7 s
  4. otter.ro at 3.6 s3.6 s
  5. otter.ro at 4.6 s4.6 s
  6. otter.ro at 5.5 s5.5 s
  7. otter.ro at 6.4 s6.4 s
  8. otter.ro at 7.3 s7.3 s

Speed

9 to fix35
  • Render-blocking requests

    2.6 s

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

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 81). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.8 s

    A phone's processor spends 6.8 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4,505 HTML elements

    The page has 4,505 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    960 ms · 160 KiB

    About 160 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 960 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, cookiebot.eu and Nosto and others), adding 631 KiB and 710 ms of main-thread time.

  • Improve image delivery

    300 ms · 210 KiB

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

  • Use efficient cache lifetimes

    150 ms · 290 KiB

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

  • Reduce unused JavaScript

    403 KiB

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

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 36 KiB

    Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Phones get a much slower page than desktops

    Desktop scores 81 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 261 ms

    261 ms

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

Core Web Vitals

9 to fix100
  • 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.

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

  • Time to Interactive: 17.3 s

    17.3 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

    Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Tap response (INP) got 55% slower for real visitors

    +55%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 964 ms

    964 ms

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 143 ms

    143 ms

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

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

    -22%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix75
  • Page weight: 2.4 MB in 160 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 160 requests on a phone: scripts 1.6 MB (78), images 388 KiB (28) and stylesheets 206 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    87 KiB

    1 image is downloaded at several times the size a phone draws it, for example Skechers.png at 1,200 px wide, shown at 102 px. Resized copies would save about 87 KiB.

  • About 0.7 g of CO₂ per visit

    0.67 g

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

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8795
  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 7 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 9286
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 403 internal links, 8 external

    The homepage links to 403 pages on otter.ro and 8 external pages.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Mii de modele de incaltaminte si genti. ✅ Livrare rapida acasa sau in locker. ✅ Retur gratuit. Descopera acum noua cole…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Otter Romania | Magazin Online de Incaltaminte”.

  • Canonical URL set

    The canonical URL is https://www.otter.ro/.

  • 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://www.otter.ro/media/sitemap/otter_index_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.otter.ro/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.

3 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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

4 to fix78
  • 1 linked page hidden from search

    https://www.otter.ro/guestwishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.otter.ro/contact, https://www.otter.ro/guestwishlist and https://www.otter.ro/links/retro-sport-style/pentru/femei have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.otter.ro/reduceri/pentru/femei, whose canonical is https://www.otter.ro/reduceri. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.otter.ro/contact and https://www.otter.ro/femei have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 187 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 10 broken images

    10 images failed to load on a phone, for example https://www.otter.ro/.

  • 12 small tap targets

    12 of 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d21m4dsqdd3b9h.cloudfront.net/magento-668fd03c/search/templates/main/deployment/17…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

  • Only about 226 words

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

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • 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

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 23 other companies contacted

    Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 otter.ro, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Magento

Company

Founded
1999
Headquarters
Chiajna

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on otter.ro, including 18 speed issues, 2 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