Website review, no card needed

oppizi.com logo

oppizi.com website review

Visit site (opens in a new tab)Reviewed 2 November 202630 issues · 80 checks

This review found 30 issues worth fixing on oppizi.com, 11 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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.6 s2.3 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.3 s
May 23, 20263.2 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.4 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.3 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.1 s
Oct 17, 20262.9 s
Oct 24, 20262.6 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
355 ms198 msMay 16Oct 31222 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026297 ms
May 23, 2026306 ms
May 30, 2026298 ms
Jun 6, 2026300 ms
Jun 13, 2026300 ms
Jun 20, 2026303 ms
Jun 27, 2026322 ms
Jul 4, 2026326 ms
Jul 11, 2026337 ms
Jul 18, 2026321 ms
Jul 25, 2026310 ms
Aug 1, 2026310 ms
Aug 8, 2026304 ms
Aug 15, 2026294 ms
Aug 22, 2026312 ms
Aug 29, 2026305 ms
Sep 5, 2026299 ms
Sep 12, 2026298 ms
Sep 19, 2026275 ms
Sep 26, 2026270 ms
Oct 3, 2026249 ms
Oct 10, 2026238 ms
Oct 17, 2026228 ms
Oct 24, 2026216 ms
Oct 31, 2026222 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 oppizi.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix37
  • Reduce unused JavaScript

    1.7 s · 559 KiB

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

  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 6.4 s

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

  • 3,720 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (TikTok, Cookiebot and IPONWEB and others), adding 508 KiB and 561 ms of main-thread time.

  • Use efficient cache lifetimes

    200 ms · 299 KiB

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

  • 18 long tasks on the main thread

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

  • TikTok adds 281 ms

    281 ms

    TikTok costs a phone 281 ms of main-thread work and 169 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

    150 ms · 50 KiB

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

  • Render-blocking requests

    150 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Improve image delivery

    30 KiB

    1 image could be 30 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    13 KiB

    About 13 KiB of CSS is downloaded but never applied on this page.

  • 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: 18 ms

    18 ms

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

Core Web Vitals

9 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: 9.2 s

    9.2 s

    Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Oppizi OS dashboard — campaign overview, active campaigns a…”.

  • Time to Interactive: 13.0 s

    13.0 s

    The page becomes fully interactive after 13.0 s. Good is under 3.8 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: 3.9 s

    3.9 s

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

  • 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: 211 ms

    211 ms

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

  • 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: 1.3 s

    1.3 s

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.03

    0.03

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

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

    -27%

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

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

    -22%

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    section-light.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.50 g

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

3 checks passed
  • Page weight: 1.8 MB in 144 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 144 requests on a phone: scripts 1.4 MB (40), other files 119 KiB (89) and fonts 98 KiB (2). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9796
  • 10 text elements with low contrast

    10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate 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.

2 checks passed
  • Every image has alt text

    All 109 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

Google 100100
  • 142 internal links, 9 external

    The homepage links to 142 pages on oppizi.com and 9 external pages.

8 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “The leading offline marketing platform to plan, launch, and measure every offline channel.”.

  • One H1 headline

    Your main headline reads: “Offline marketingnow fully agentic”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Oppizi - The agentic offline marketing platform”.

  • Canonical URL set

    The canonical URL is https://oppizi.com/us/en/.

  • Structured data in place

    Structured data found: FAQPage, Organization, WebPage 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://oppizi.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix93
  • 2 pages share a meta description

    https://oppizi.com/us/en/platform/oppizi-os and https://oppizi.com/us/en/platform/integrations use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://oppizi.com/us/en/get-started has 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 63 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix69
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 88 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 1,312 words of copy

    The homepage carries about 1,312 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: “Get started” and “Book a demo”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Get started”, “Book a demo” and “Learn more about Direct Mail”.

  • 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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 oppizi.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
Next.js
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on oppizi.com, including 17 speed issues and 5 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