Programmable

Website review, no card needed

univers.com logo

univers.com website review

Visit site (opens in a new tab)Reviewed 31 October 202628 issues · 82 checks

This review found 28 issues worth fixing on univers.com, 9 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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

Site score

80B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.6 s2.7 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.1 s
Jul 25, 20263.1 s
Aug 1, 20263.0 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.3 s
Sep 26, 20263.5 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
212 ms108 msMay 9Oct 24126 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026127 ms
May 16, 2026136 ms
May 23, 2026138 ms
May 30, 2026163 ms
Jun 6, 2026200 ms
Jun 13, 2026173 ms
Jun 20, 2026150 ms
Jun 27, 2026133 ms
Jul 4, 2026123 ms
Jul 11, 2026123 ms
Jul 18, 2026127 ms
Jul 25, 2026129 ms
Aug 1, 2026137 ms
Aug 8, 2026144 ms
Aug 15, 2026133 ms
Aug 22, 2026134 ms
Aug 29, 2026140 ms
Sep 5, 2026137 ms
Sep 12, 2026152 ms
Sep 19, 2026152 ms
Sep 26, 2026146 ms
Oct 3, 2026124 ms
Oct 10, 2026120 ms
Oct 17, 2026123 ms
Oct 24, 2026126 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

univers.com (opens in a new tab)
Full-page screenshot of univers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix58

  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 388 KiB

    About 388 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.

  • Use efficient cache lifetimes

    400 ms · 46 KiB

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

  • Reduce unused JavaScript

    300 ms · 56 KiB

    About 56 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 1,835 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Cookiebot, LinkedIn Ads and Cloudflare CDN and others), adding 456 KiB and 218 ms of main-thread time.

  • Improve image delivery

    126 KiB

    4 images could be 126 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 84 ms. During a long task the page ignores taps.

  • Minify CSS

    56 KiB

    56 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

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

2 checks passed

  • Main-thread work: 1.7 s

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

  • Server response: 68 ms

    68 ms

    Your server sent the HTML in 68 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.

  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Physical AI That Runs The World's Critical Operations”.

  • Speed Index: 8.0 s

    8.0 s

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

  • Time to Interactive: 9.8 s

    9.8 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 30 images without width and height

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

  • 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 127 ms to 126 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -9%

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

4 checks passed

  • Real-user INP: 140 ms

    140 ms

    Real visitors wait 140 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.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 17 ms

    17 ms

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

Images and page weight

1 to fix85

  • Page weight: 3.5 MB in 128 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 128 requests on a phone: images 1.6 MB (25), HTML 929 KiB (2) and scripts 771 KiB (62). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (158 KiB) 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.

  • About 1.0 g of CO₂ per visit

    0.98 g

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

2 checks passed

  • 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

7 to fixGoogle 9191

  • 19 text elements with low contrast

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

  • 3 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed

  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 8581

  • No meta description

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

  • Title is short (14 characters)

    Your title is only 14 characters: “Home - Univers”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 70 internal links, 1 external

    The homepage links to 70 pages on univers.com and 1 external page.

6 checks passed

  • One H1 headline

    Your main headline reads: “Physical AI That Runs The World's Critical Operations”.

  • Canonical URL set

    The canonical URL is https://univers.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://univers.com/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

    There is no https://univers.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 (1,556 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95

  • 6 pages without a meta description

    https://univers.com/energy-utilities, https://univers.com/about-us, https://univers.com/careers, https://univers.com/news, https://univers.com/resources and https://univers.com/customer-stories have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages slow to respond

    https://univers.com/built-environment, https://univers.com/transportation-logistics, https://univers.com/industrial-manufacturing, https://univers.com/singapore-story, https://univers.com/resources and https://univers.com/customer-stories took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed

  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 an H1

    Each page we checked has a main headline.

  • 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

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92

  • 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 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 1,484 words of copy

    The homepage carries about 1,484 words of visible text.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more →” and “Contact Us”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Learn more →”, “Contact Us” and “Talk to us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and 14 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 8 other companies contacted

    Loading the homepage contacts 8 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 univers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on univers.com, including 15 speed issues, 3 SEO issues and 1 conversion gap. 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