Website review, no card needed

okmobility.com logo

okmobility.com website review

Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 85 checks

This review found 43 issues worth fixing on okmobility.com, 18 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
4.6 s3.7 sMay 30Nov 143.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.3 s
Jun 6, 20264.3 s
Jun 13, 20264.3 s
Jun 20, 20264.3 s
Jun 27, 20264.4 s
Jul 4, 20264.4 s
Jul 11, 20264.4 s
Jul 18, 20264.4 s
Jul 25, 20264.4 s
Aug 1, 20264.3 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.5 s
Sep 5, 20264.4 s
Sep 12, 20264.4 s
Sep 19, 20264.3 s
Sep 26, 20264.2 s
Oct 3, 20264.1 s
Oct 10, 20264.1 s
Oct 17, 20264.0 s
Oct 24, 20263.9 s
Oct 31, 20263.9 s
Nov 7, 20263.8 s
Nov 14, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
316 ms229 msMay 30Nov 14272 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026239 ms
Jun 6, 2026246 ms
Jun 13, 2026251 ms
Jun 20, 2026255 ms
Jun 27, 2026258 ms
Jul 4, 2026260 ms
Jul 11, 2026261 ms
Jul 18, 2026261 ms
Jul 25, 2026262 ms
Aug 1, 2026265 ms
Aug 8, 2026272 ms
Aug 15, 2026285 ms
Aug 22, 2026293 ms
Aug 29, 2026303 ms
Sep 5, 2026306 ms
Sep 12, 2026304 ms
Sep 19, 2026303 ms
Sep 26, 2026298 ms
Oct 3, 2026294 ms
Oct 10, 2026287 ms
Oct 17, 2026281 ms
Oct 24, 2026277 ms
Oct 31, 2026274 ms
Nov 7, 2026272 ms
Nov 14, 2026272 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 okmobility.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

14 to fix35
  • Use efficient cache lifetimes

    6.9 s · 19.7 MB

    126 files are served with short cache lifetimes, so returning visitors download them again (19.7 MB).

  • Improve image delivery

    3.5 s · 1.1 MB

    6 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

  • Google Tag Manager adds 1.8 s

    1.8 s

    Google Tag Manager costs a phone 1.8 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 35

    35/100

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

  • 7,633 HTML elements

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

  • Main-thread work: 7.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and opticksprotection.com and others), adding 3.3 MB and 2.9 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 148 KiB

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

  • Google CDN adds 445 ms

    445 ms

    Google CDN costs a phone 445 ms of main-thread work and 742 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.

  • 20 long tasks on the main thread

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

  • embedsocial.com adds 160 ms

    160 ms

    embedsocial.com costs a phone 160 ms of main-thread work and 518 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.

  • Cookiebot adds 106 ms

    106 ms

    Cookiebot costs a phone 106 ms of main-thread work and 362 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.

  • Legacy JavaScript

    9 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

8 to fix67
  • 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: 10.4 s

    10.4 s

    Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BLACK FRIDAY”.

  • Time to Interactive: 31.8 s

    31.8 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user INP: 317 ms

    317 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 26 images without width and height

    26 images have no width and height attributes, so the layout jumps as each one loads.

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

    +12%

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

6 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 570 ms

    570 ms

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

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

    -12%

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

  • Cumulative Layout Shift: 0.097

    0.097

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

Images and page weight

4 to fix38
  • Page weight: 24.2 MB in 326 requests

    24.2 MB

    Your homepage downloads 24.2 MB in 326 requests on a phone: media 11.9 MB (3), images 7.4 MB (139) and scripts 3.0 MB (98). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.

  • 22 images in older formats

    22 images (4.5 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 9 images below the first screen load straight away

    9 images further down the page (2.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.8 g of CO₂ per visit

    6.85 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 10091
  • autocomplete attribute must be used correctly (3 elements)

    autocomplete attribute must be used correctly: 3 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • ARIA role should be appropriate for the element (12 elements)

    ARIA role should be appropriate for the element: 12 elements on the page fail this check, rated minor 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.

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 9287
  • 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, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 64 internal links, 11 external

    The homepage links to 64 pages on okmobility.com and 11 external pages.

5 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Rental, transfer, subscription, leasing, and car purchase. 70+ destinations. Mobility as a synonym for happiness! Love …”.

  • One H1 headline

    Your main headline reads: “The Global Mobility Platform”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “OK Mobility - The Global Mobility Platform”.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

100
  • No llms.txt

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

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

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 3 pages share a title

    https://okmobility.com/en/rent, https://okmobility.com/en/rent/corporate and https://okmobility.com/en/club all use the title “OK Mobility”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://okmobility.com/en/rent, https://okmobility.com/es/renting, https://okmobility.com/en/rent/corporate and https://okmobility.com/en/club have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://okmobility.com/en/rent, https://okmobility.com/en/app, https://okmobility.com/en/rent/corporate and https://okmobility.com/en/club 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 30 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • 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.

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

  • About 576 words of copy

    The homepage carries about 576 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book Standard range” and “Book a transfer”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “BLACK FRIDAY buy-car”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 okmobility.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
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Headquarters
Palma

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on okmobility.com, including 22 speed issues, 4 SEO issues 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