Website review, no card needed
ucbenvironmental.com website review
Visit site (opens in a new tab)Reviewed 23 October 202632 issues · 81 checks
This review found 32 issues worth fixing on ucbenvironmental.com, 12 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
74C- #67,772 of 96,293 reviewed websitesbeats 26%
- #40,847 of 52,137 online storesbeats 18%
- #1,218 of 2,240 WooCommerce storesbeats 39%
Closest competitors among WooCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.6 s
3.2 s
3.7 s
4.2 s
Speed
Use efficient cache lifetimes
6.4 s · 4.8 MB185 files are served with short cache lifetimes, so returning visitors download them again (4.8 MB).
Improve image delivery
1.8 s · 2.4 MB71 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
3.1 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Reduce unused CSS
900 ms · 171 KiBAbout 171 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 64). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 298 KiBAbout 298 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 819 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, userway.org and Google Fonts and others), adding 351 KiB and 268 ms of main-thread time.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sustainable Sustainability™ Good for the planet. Great for …”.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
First Contentful Paint: 4.9 s
4.9 sThe first text or image appears after 4.9 s on a phone. Good is under 1.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Total Blocking Time: 80 ms
80 msScripts block the page for only 80 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 199 requests
5.2 MBYour homepage downloads 5.2 MB in 199 requests on a phone: images 3.9 MB (91), scripts 733 KiB (60) and fonts 286 KiB (5). Under 2 MB keeps phones on slow connections fast.
31 images in older formats
31 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.
33 images below the first screen load straight away
33 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
49 KiB2 images are downloaded at several times the size a phone draws them, for example logo2.png at 432 px wide, shown at 120 px. Resized copies would save about 49 KiB.
About 1.5 g of CO₂ per visit
1.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements must only use permitted ARIA attributes (72 elements)
Elements must only use permitted ARIA attributes: 72 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 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 (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 84 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 5 failed. 3 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.
Title is long (79 characters)
Your title is 79 characters, so Google will cut it off around 60: “UCBEnvironmental – A family of companies focused on Sustainable Sustainability™”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
24 internal links, 12 external
The homepage links to 24 pages on ucbenvironmental.com and 12 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.ucbenvironmental.com/.
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://www.ucbenvironmental.com/wp-sitemap.xml.
AI search readiness
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.ucbenvironmental.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 (386 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.ucbenvironmental.com/about-us, https://www.ucbenvironmental.com/the-team, https://www.ucbenvironmental.com/contact-us and https://www.ucbenvironmental.com/join-us have no meta description, so Google writes the search snippet from whatever text it finds.
1 page with very little text
https://www.ucbenvironmental.com/contact-us has 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.
1 page slow to respond
https://www.ucbenvironmental.com/join-us took over 3 s to send its HTML from our server.
4 internal pages checked
We fetched 4 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 4 pages we checked loaded without an error.
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 4 pages that loaded have a <title>.
Best practices
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 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 355 words of copy
The homepage carries about 355 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”.
15 calls to action
The homepage has 15 calls to action, for example “Contact Us”, “Join Us” and “Learn More”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
6 other companies contacted
Loading the homepage contacts 6 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 ucbenvironmental.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
Company
- Employees
- 21
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on ucbenvironmental.com, including 12 speed issues, 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.