Website review, no card needed

omri.org logo

omri.org website review

Visit site (opens in a new tab)Reviewed 22 October 202640 issues · 78 checks

This review found 40 issues worth fixing on omri.org, 17 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
5.2 s4.4 sMay 2Oct 174.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.7 s
May 9, 20264.7 s
May 16, 20264.6 s
May 23, 20264.6 s
May 30, 20264.7 s
Jun 6, 20264.8 s
Jun 13, 20264.9 s
Jun 20, 20265.1 s
Jun 27, 20264.9 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.7 s
Jul 25, 20264.6 s
Aug 1, 20264.6 s
Aug 8, 20264.8 s
Aug 15, 20264.6 s
Aug 22, 20264.7 s
Aug 29, 20264.7 s
Sep 5, 20264.5 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.7 s
Oct 3, 20264.8 s
Oct 10, 20264.9 s
Oct 17, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
133 ms99 msMay 2Oct 17119 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026113 ms
May 9, 2026112 ms
May 16, 2026107 ms
May 23, 2026104 ms
May 30, 2026103 ms
Jun 6, 2026103 ms
Jun 13, 2026120 ms
Jun 20, 2026121 ms
Jun 27, 2026129 ms
Jul 4, 2026129 ms
Jul 11, 2026120 ms
Jul 18, 2026119 ms
Jul 25, 2026117 ms
Aug 1, 2026114 ms
Aug 8, 2026114 ms
Aug 15, 2026114 ms
Aug 22, 2026110 ms
Aug 29, 2026109 ms
Sep 5, 2026108 ms
Sep 12, 2026104 ms
Sep 19, 2026112 ms
Sep 26, 2026113 ms
Oct 3, 2026117 ms
Oct 10, 2026120 ms
Oct 17, 2026119 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 omri.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. omri.org at 0.9 s0.9 s
  2. omri.org at 1.7 s1.7 s
  3. omri.org at 2.6 s2.6 s
  4. omri.org at 3.4 s3.4 s
  5. omri.org at 4.3 s4.3 s
  6. omri.org at 5.1 s5.1 s
  7. omri.org at 6.0 s6.0 s
  8. omri.org at 6.8 s6.8 s

Speed

5 to fix51
  • Improve image delivery

    8.4 s · 1.7 MB

    5 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.4 s faster on a phone.

  • Render-blocking requests

    7.3 s

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

  • Reduce unused JavaScript

    1.8 s · 244 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 286 KiB

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

  • Mobile performance score: 51

    51/100

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

  • Minify JavaScript

    160 ms · 87 KiB

    87 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    160 ms · 62 KiB

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

  • Minify CSS

    160 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 223 KiB and 117 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • 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: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 179 ms 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

11 to fix33
  • 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 LCP: 5.6 s

    5.6 s

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

  • Real-user CLS: 0.28

    0.28

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Largest Contentful Paint: 19.1 s

    19.1 s

    Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OMRI’s mission is to cultivate organic integrity through kn…”.

  • Time to Interactive: 19.1 s

    19.1 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Speed Index: 9.3 s

    9.3 s

    Visually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 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.

  • Cumulative Layout Shift: 0.145

    0.145

    The layout shifts by 0.145 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

2 checks passed
  • Real-user INP: 78 ms

    78 ms

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

  • Total Blocking Time: 106 ms

    106 ms

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

Images and page weight

2 to fix75
  • Page weight: 3.1 MB in 65 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 65 requests on a phone: images 2.5 MB (16), scripts 470 KiB (15) and stylesheets 120 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    209 KiB

    2 images are downloaded at several times the size a phone draws them, for example Wheelbarrow.png at 1,667 px wide, shown at 110 px. Resized copies would save about 209 KiB.

  • 3 images in older formats

    3 images (253 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 0.9 g of CO₂ per visit

    0.87 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 6681
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

  • 9 images without alt text

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

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

    All page content should be contained by landmarks: 21 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 21 automated accessibility rules passed

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

SEO

7 to fixGoogle 7366
  • No meta description

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

  • Title is long (86 characters)

    Your title is 86 characters, so Google will cut it off around 60: “Welcome to the Organic Materials Review Institute | Organic Materials Review Institute”.

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

  • No XML sitemap

    No XML sitemap at https://www.omri.org/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at omri.org/robots.txt, the first file search crawlers ask for.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 110 internal links, 15 external

    The homepage links to 110 pages on omri.org and 15 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to the Organic Materials Review Institute”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix81
  • 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.omri.org/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.

1 checks passed
  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 6 small tap targets

    6 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

  • No map or directions link

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

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

    The homepage carries about 410 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET STARTED” and “Learn more about our privacy policy”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Request new password” and “GET STARTED”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on omri.org, including 16 speed issues, 7 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