Website review, no card needed

oettingerdavidoff.com logo

oettingerdavidoff.com website review

Visit site (opens in a new tab)Reviewed 25 October 202627 issues · 74 checks

This review found 27 issues worth fixing on oettingerdavidoff.com, 8 of them high impact, across 74 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
2.6 s1.9 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.2 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.2 s
Aug 29, 20262.5 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.2 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
115 ms83 msMay 2Oct 1787 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026100 ms
May 9, 2026104 ms
May 16, 2026111 ms
May 23, 2026104 ms
May 30, 2026103 ms
Jun 6, 202699 ms
Jun 13, 202690 ms
Jun 20, 202692 ms
Jun 27, 202694 ms
Jul 4, 202694 ms
Jul 11, 2026102 ms
Jul 18, 2026104 ms
Jul 25, 202698 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202695 ms
Aug 22, 202687 ms
Aug 29, 202692 ms
Sep 5, 202693 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202690 ms
Oct 3, 202687 ms
Oct 10, 202689 ms
Oct 17, 202687 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 oettingerdavidoff.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix63
  • Reduce unused JavaScript

    1.2 s · 242 KiB

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

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 59). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    750 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, userway.org and Usercentrics CMP and others), adding 3.5 MB and 166 ms of main-thread time.

  • Minify JavaScript

    300 ms · 50 KiB

    50 KiB could be saved by minifying JavaScript.

  • b-cdn.net adds 0 ms

    0 ms

    b-cdn.net costs a phone 0 ms of main-thread work and 2.8 MB 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.

  • Use efficient cache lifetimes

    200 ms · 56 KiB

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • Improve image delivery

    81 KiB

    3 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Reduce unused CSS

    14 KiB

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

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

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 14 ms

    14 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.94

    0.94

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

  • Largest Contentful Paint: 8.4 s

    8.4 s

    Your largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “150 years of Oettinger Davidoff – a century and a half of p…”.

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Time to Interactive: 8.5 s

    8.5 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

7 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: 88 ms

    88 ms

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 416 ms

    416 ms

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

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

    -14%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 8 ms

    8 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.9 MB in 98 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 98 requests on a phone: media 2.8 MB (1), scripts 805 KiB (45) and images 272 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.12 g

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

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

  • Images are sized for phones

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

Accessibility

1 to fix96
  • 4 text elements with low contrast

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

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

SEO

5 to fixGoogle 10077
  • Title is short (23 characters)

    Your title is only 23 characters: “Oettinger Davidoff Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • Meta description is long (220 characters)

    Your meta description is 220 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 52 internal links, 3 external

    The homepage links to 52 pages on oettingerdavidoff.com and 3 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “150 years of Oettinger Davidoff – a century and a half of passion, innovation and integrity marked by visionary ideas, …”.

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

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

2 to fix85
  • 2 linked pages hidden from search

    https://www.oettingerdavidoff.com/about-us and https://www.oettingerdavidoff.com/about-us/one-hundred-and-fifty-years are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.oettingerdavidoff.com/crop-to-shop/production and https://www.oettingerdavidoff.com/crop-to-shop/distribution all use the title “Production | Oettinger Davidoff”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 2 small tap targets

    2 of 6 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • 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 528 words of copy

    The homepage carries about 528 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “CROP TO SHOP”, “Contact Us” and “JOIN OUR TEAM”.

  • Analytics in place

    Analytics detected: Google Analytics.

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 (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

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

  • 15 other companies contacted

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

1 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) 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 oettingerdavidoff.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
Analytics
Google Analytics
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on oettingerdavidoff.com, including 12 speed issues, 5 SEO issues and 3 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