Website review, no card needed
urus.org website review
Visit site (opens in a new tab)Reviewed 28 October 202634 issues · 81 checks
This review found 34 issues worth fixing on urus.org, 15 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 109 ms |
| May 16, 2026 | 105 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 106 ms |
| Jul 4, 2026 | 106 ms |
| Jul 11, 2026 | 101 ms |
| Jul 18, 2026 | 97 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 103 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 84 ms |
| Sep 12, 2026 | 78 ms |
| Sep 19, 2026 | 81 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 82 ms |
| Oct 10, 2026 | 83 ms |
| Oct 17, 2026 | 84 ms |
| Oct 24, 2026 | 80 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
Speed
Render-blocking requests
9.6 s40 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.6 s.
Reduce unused JavaScript
1.2 s · 141 KiBAbout 141 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Improve image delivery
2.5 MB7 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 75 KiBAbout 75 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.
1,778 HTML elements
The page has 1,778 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
1 third-party service on the page
1 third-party service load with your homepage (Cookiebot), adding 159 KiB and 214 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Use efficient cache lifetimes
34 KiB4 files are served with short cache lifetimes, so returning visitors download them again (34 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 657 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 9.5 s
9.5 sThe first text or image appears after 9.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 25.9 s
25.9 sYour largest element takes 25.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 27.1 s
27.1 sThe page becomes fully interactive after 27.1 s. Good is under 3.8 s.
Speed Index: 9.7 s
9.7 sVisually, the page fills in at 9.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.13
0.13For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.
7 checks passed
Real-user INP: 79 ms
79 msReal visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 756 ms
756 msReal visitors wait 756 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 109 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 1 ms
1 msScripts block the page for only 1 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 7.5 MB in 148 requests
7.5 MBYour homepage downloads 7.5 MB in 148 requests on a phone: images 5.4 MB (52), fonts 1.4 MB (5) and scripts 650 KiB (52). Under 2 MB keeps phones on slow connections fast.
About 2.1 g of CO₂ per visit
2.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 256.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
75 internal links, 25 external
The homepage links to 75 pages on urus.org and 25 external pages.
6 checks passed
Title: 44 characters
Your title is a healthy 44 characters: “URUS - URUS | Better Cows for a Better World”.
Canonical URL set
The canonical URL is https://urus.org/.
Structured data in place
Structured data found: BreadcrumbList, 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://urus.org/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://urus.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.
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 (735 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://urus.org/contact-us and https://urus.org/contact all use the title “Contact - URUS | Better Cows for a Better World”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://urus.org/who-we-are, https://urus.org/executive-board, https://urus.org/contact-us, https://urus.org/agriwebb, https://urus.org/alta-genetics and https://urus.org/genetics-australia and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://urus.org/contact, whose canonical is https://urus.org/contact-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://urus.org/who-we-are, https://urus.org/executive-board, https://urus.org/contact-us, https://urus.org/agriwebb, https://urus.org/alta-genetics and https://urus.org/genetics-australia and 9 others 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 18 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 small tap targets
3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 312 words of copy
The homepage carries about 312 words of visible text.
2 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Contact Us”, “Learn More” and “LEARN MORE”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 urus.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on urus.org, including 13 speed issues, 4 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.