Website review, no card needed

omniabrush.com logo

omniabrush.com website review

Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 84 checks

This review found 39 issues worth fixing on omniabrush.com, 11 of them high impact, across 84 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.0 s1.2 sMay 30Nov 141.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 20, 20261.6 s
Jun 27, 20261.5 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Nov 14, 20261.5 s

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 omniabrush.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. omniabrush.com at 0.6 s0.6 s
  2. omniabrush.com at 1.2 s1.2 s
  3. omniabrush.com at 1.8 s1.8 s
  4. omniabrush.com at 2.4 s2.4 s
  5. omniabrush.com at 3.1 s3.1 s
  6. omniabrush.com at 3.7 s3.7 s
  7. omniabrush.com at 4.3 s4.3 s
  8. omniabrush.com at 4.9 s4.9 s

Speed

9 to fix53
  • Reduce unused JavaScript

    2.3 s · 465 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    900 ms · 343 KiB

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

  • Mobile performance score: 53

    53/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Klaviyo and others), adding 1.9 MB and 670 ms of main-thread time.

  • Google Tag Manager adds 426 ms

    426 ms

    Google Tag Manager costs a phone 426 ms of main-thread work and 493 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

    300 ms · 54 KiB

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

  • Legacy JavaScript

    300 ms · 42 KiB

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

  • Shopify adds 19 ms

    19 ms

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

  • 5 long tasks on the main thread

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

  • Font display

    200 ms

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

  • Use efficient cache lifetimes

    19 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (19 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 CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 15 ms

    15 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 17.4 s

    17.4 s

    Your largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “OMNIA Pros”.

  • Time to Interactive: 17.4 s

    17.4 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 409 ms

    409 ms

    Scripts block taps and scrolling for 409 ms in total while the page loads. Good is under 200 ms.

  • 1 image without width and height

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

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

    103 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 217 ms

    217 ms

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

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

    -20%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.5 s 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).

Images and page weight

5 to fix50
  • 1 image over 500 KB

    Homepage_-_Warrenty_image_-_Desktop.webp weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.9 MB in 201 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 201 requests on a phone: images 1.5 MB (18), scripts 1.3 MB (68) and other files 745 KiB (92). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (1.3 MB) 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.

  • An image on the first screen is lazy-loaded

    Banner3-Aritist-Omnia-Mobile.png 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).

  • 1 image far larger than shown

    58 KiB

    1 image is downloaded at several times the size a phone draws it, for example Homepage_-_Warrenty_image_-_Mobile2.webp at 1,384 px wide, shown at 371 px. Resized copies would save about 58 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (163 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.10 g

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

Accessibility

6 to fixGoogle 8992
  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

    2 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 (30 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 10082
  • Title is short (26 characters)

    Your title is only 26 characters: “OMNIA® Brush – OMNIA Brush”. 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 long (279 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 117 internal links, 9 external

    The homepage links to 117 pages on omniabrush.com and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “<img class="" src="//omniabrush.com/cdn/shop/files/omnia_logo_1000x1000.png?v=1614317844" alt="" itemprop="logo" loadin…”.

  • Canonical URL set

    The canonical URL is https://omniabrush.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://omniabrush.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://omniabrush.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 (346 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://omniabrush.com/collections 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 35 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    1 page 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.

  • Every page has a meta description

    All 1 page 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 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187005561&Ver=2&mid=44aa6819-e46e-4d5d-9972-4e502a23f833&bo=1&sid=48b377b0e1ef11f19f9505c48a791405&vid=48b3b330e1ef11f1a2fd81cfcd759ec7&vids=1&msclkid=N&pi=918639831&l.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://omniabrush.com/cdn/shop/t/229/assets/zify-products-slider.css?v=8793' because its …”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • Only about 176 words

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

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

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “SHOP AT NORDSTROM”, “SHOP AT BLOOMINGDALES” and “Learn more about Jalia's favorites here.”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies (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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 omniabrush.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · amazonaws.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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on omniabrush.com, including 15 speed issues, 4 SEO issues and 4 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