Website review, no card needed

unox.com logo

unox.com website review

Visit site (opens in a new tab)Reviewed 27 October 202625 issues · 71 checks

This review found 25 issues worth fixing on unox.com, 5 of them high impact, across 71 checks. The most urgent: fails Core Web Vitals for real visitors. 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
1.7 s1.1 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.1 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
161 ms133 msMay 9Oct 24152 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026142 ms
May 16, 2026142 ms
May 23, 2026137 ms
May 30, 2026144 ms
Jun 6, 2026139 ms
Jun 13, 2026138 ms
Jun 20, 2026156 ms
Jun 27, 2026151 ms
Jul 4, 2026158 ms
Jul 11, 2026158 ms
Jul 18, 2026146 ms
Jul 25, 2026148 ms
Aug 1, 2026137 ms
Aug 8, 2026143 ms
Aug 15, 2026144 ms
Aug 22, 2026145 ms
Aug 29, 2026145 ms
Sep 5, 2026142 ms
Sep 12, 2026136 ms
Sep 19, 2026142 ms
Sep 26, 2026144 ms
Oct 3, 2026145 ms
Oct 10, 2026145 ms
Oct 17, 2026146 ms
Oct 24, 2026152 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 unox.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix64
  • Improve image delivery

    150 ms · 982 KiB

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

  • Mobile performance score: 64

    64/100

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

  • Render-blocking requests

    650 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 650 ms.

  • Reduce unused CSS

    300 ms · 62 KiB

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

  • 2 long tasks on the main thread

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

  • 2,482 HTML elements

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

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 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 98 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 1 third-party service on the page

    1 third-party service load with your homepage (LinkedIn Ads), adding 7 KiB and 8 ms of main-thread time.

  • Forced reflow

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 27 ms

    27 ms

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

Core Web Vitals

6 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: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Smiling male Chef standing in a kitchen holding a knife and…”.

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Real-user TTFB: 843 ms

    843 ms

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

7 checks passed
  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (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.

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

    -14%

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

  • Total Blocking Time: 174 ms

    174 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix65
  • 11 images far larger than shown

    619 KiB

    11 images are downloaded at several times the size a phone draws them, for example commercial-ovens-supermarkets-7.webp at 1,024 px wide, shown at 320 px. Resized copies would save about 619 KiB.

  • Page weight: 3.0 MB in 80 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 80 requests on a phone: images 2.4 MB (24), scripts 355 KiB (48) and HTML 141 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.85 g

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

3 to fixGoogle 10096
  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 87 elements on the page fail this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 74 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 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 10090
  • Title is short (23 characters)

    Your title is only 23 characters: “Commercial ovens | UNOX”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 113 internal links, 8 external

    The homepage links to 113 pages on unox.com and 8 external pages.

6 checks passed
  • Meta description: 111 characters

    Your meta description is 111 characters: “Optimize your kitchen’s efficiency with Unox’s versatile combi, convection, and speed cooking commercial ovens.”.

  • One H1 headline

    Your main headline reads: “Building success with smart commercial ovens.”.

  • Canonical URL set

    The canonical URL is https://www.unox.com/us_us/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.unox.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://unox.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://unox.com/us_us/configurator and https://unox.com/us_us/ovens/combi/commercial-countertop-combi-ovens are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://unox.com/us_us/company/service-locator, https://unox.com/us_us/configurator, https://unox.com/us_us/ovens/combi/commercial-countertop-combi-ovens, https://unox.com/us_us/ovens/combi/commercial-trolley-combi-ovens and https://unox.com/us_us/individual-cooking-experience have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://unox.com/us_us/company/service-locator, https://unox.com/us_us/configurator, https://unox.com/us_us/accessories/xuc175 and https://unox.com/us_us/accessories/xadoa-11-r 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 48 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.

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 2 trust badges. 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.

  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

  • 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 2,116 words of copy

    The homepage carries about 2,116 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: “TRY IT FOR FREE”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “TRY IT FOR FREE” and “SUBSCRIBE”.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 unox.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
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on unox.com, including 12 speed issues, 2 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