otip.com website review

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

About 638 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google Optimize and jQuery CDN and others), adding 1.3 MB and 627 ms of main-thread time.

Google Tag Manager costs a phone 421 ms of main-thread work and 777 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.

57 KiB could be saved by minifying JavaScript.

23 KiB could be saved by minifying CSS.

14 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 40.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Looking for help? Get the answers you need with our FAQs, s…”.

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

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

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

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

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

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

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

Your homepage downloads 8.7 MB in 104 requests on a phone: images 6.8 MB (41), scripts 1.6 MB (34) and stylesheets 144 KiB (15). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

[aria-*] attributes do not have valid values (1 element).

7 elements hidden from screen readers can still receive keyboard focus.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Elements with role="none" or role="presentation" have conflicts (1 element).

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

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

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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 is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

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

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 errors were logged to the browser console during Google's test (“Refused to apply style from 'https://getbootstrap.com/docs/5.3/assets/css/docs.css' because its MIM…”).

4 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 110 words of visible text; thin pages give Google and first-time buyers little to go on.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.