Website review, no card needed

ornexis.com logo

ornexis.com website review

Visit site (opens in a new tab)Reviewed 20 November 202624 issues · 77 checks

This review found 24 issues worth fixing on ornexis.com, 2 of them high impact, across 77 checks. The most urgent: links must have discernible text (1 element). 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.9 s1.1 sMay 30Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.3 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.4 s
Sep 5, 20261.4 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.6 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
142 ms108 msMay 30Oct 10112 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026127 ms
Jun 6, 2026131 ms
Jun 13, 2026128 ms
Jun 20, 2026120 ms
Jun 27, 2026113 ms
Jul 4, 2026115 ms
Jul 11, 2026115 ms
Jul 18, 2026118 ms
Jul 25, 2026119 ms
Aug 1, 2026119 ms
Aug 8, 2026119 ms
Aug 15, 2026117 ms
Aug 22, 2026116 ms
Aug 29, 2026116 ms
Sep 5, 2026119 ms
Sep 12, 2026122 ms
Sep 19, 2026126 ms
Sep 26, 2026134 ms
Oct 3, 2026138 ms
Oct 10, 2026112 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 ornexis.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix96
  • Render-blocking requests

    750 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and heatmap.com and others), adding 908 KiB and 533 ms of main-thread time.

  • Reduce unused JavaScript

    299 KiB

    About 299 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.0 s

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

  • Shopify adds 155 ms

    155 ms

    Shopify costs a phone 155 ms of main-thread work and 634 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.

  • Reduce unused CSS

    68 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    45 KiB

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

  • Use efficient cache lifetimes

    41 KiB

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Mobile performance score: 96

    96/100

    Your mobile performance score is 96. That is in Google's “good” band (90 and up).

  • Server response: 68 ms

    68 ms

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

Core Web Vitals

2 to fix100
  • Time to Interactive: 10.0 s

    10.0 s

    The page becomes fully interactive after 10.0 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.

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.003

    0.003

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

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

2 to fix81
  • Page weight: 2.9 MB in 391 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 391 requests on a phone: other files 1.5 MB (291), scripts 861 KiB (62) and images 291 KiB (24). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Gemini_Generated_Image_g8d9b3g8d9b3g8d9.jpg 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.8 g of CO₂ per visit

    0.83 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.4 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 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 9596
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is short (7 characters)

    Your title is only 7 characters: “Ornexis”. 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.

  • Meta description is short (7 characters)

    Your meta description is only 7 characters: “Ornexis”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Ornexis” and “Ornexis”). One clear main headline is easier for people and search engines.

  • 41 internal links, 1 external

    The homepage links to 41 pages on ornexis.com and 1 external page.

4 checks passed
  • Canonical URL set

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

  • 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://ornexis.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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix93
  • 15 pages share a meta description

    https://ornexis.com/collections/our-solutions, https://ornexis.com/pages/contact, https://ornexis.com/apps/parcelpanel, https://ornexis.com/collections/swollen-legs, https://ornexis.com/collections/migraine and https://ornexis.com/collections/restless-legs and 9 others use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://ornexis.com/collections/pain-relief-gadgets/products/ornexis-fix-arthritis-gloves, whose canonical is https://ornexis.com/products/ornexis-fix-arthritis-gloves. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages with very little text

    https://ornexis.com/collections/pain-relief-gadgets/products/ornexis-premium-ergonomic-leg-pillow and https://ornexis.com/collections/pain-relief-gadgets/products/ornexis-premium-ergonomic-travel-pillow have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 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.

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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.

  • Only about 204 words

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

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Track Your Order” and “Register / Login”.

  • 3 short forms

    3 short forms (0 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: a star rating and “9250+ Satisfied customers”.

  • Analytics in place

    Analytics detected: Meta Pixel, Microsoft Clarity and TikTok Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 2 of them by other companies (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.

  • 40 other companies contacted

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

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

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Microsoft Clarity · Omni Os Enrich Pixel · Zigpoll Customer Surveys · Swatch King · Gempages Builder · Kaching Bundles · Klaviyo Email Marketing Sms · Variant Image Swatch · Upcart · conversionbear.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on ornexis.com, including 7 speed issues, 4 SEO issues and 2 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