Website review, no card needed
lehrercumming.com website review
Visit site (opens in a new tab)Reviewed 2 November 202638 issues · 84 checks
This review found 38 issues worth fixing on lehrercumming.com, 14 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 88 ms |
| May 23, 2026 | 89 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
4.7 s · 6.0 MB19 images could be 6.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.
Render-blocking requests
2.9 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
450 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied 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, 683 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, cookiehub.eu and New Relic and others), adding 236 KiB and 337 ms of main-thread time.
Minify CSS
150 ms · 28 KiB28 KiB could be saved by minifying CSS.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.
Reduce unused JavaScript
113 KiBAbout 113 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
19 KiB2 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 78 ms
78 msYour server sent the HTML in 78 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.
Real-user CLS: 0.64
0.64For real visitors the layout shifts by 0.64 (75th percentile). Good is under 0.1.
Time to Interactive: 26.3 s
26.3 sThe page becomes fully interactive after 26.3 s. Good is under 3.8 s.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “test”.
Cumulative Layout Shift: 0.671
0.671The layout shifts by 0.671 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 88 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 81 ms
81 msReal visitors wait 81 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 181 ms
181 msScripts block the page for only 181 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.0 MB in 78 requests
8.0 MBYour homepage downloads 8.0 MB in 78 requests on a phone: images 6.8 MB (20), fonts 538 KiB (6) and scripts 375 KiB (21). Under 2 MB keeps phones on slow connections fast.
15 images in older formats
15 images (2.0 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.
2 images below the first screen load straight away
2 images further down the page (93 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.26 g of CO₂e: 270.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “Building Value Through Expertise”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
183 internal links, 5 external
The homepage links to 183 pages on lehrercumming.com and 5 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Cumming is an industry-leading, multi-faceted project management and cost consulting firm. We offer clients a comprehen…”.
Title: 54 characters
Your title is a healthy 54 characters: “Cumming Group | Project Management and Cost Consulting”.
Canonical URL set
The canonical URL is https://cumming-group.com/en/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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://cumming-group.com/sitemap_index.xml.
AI search readiness
robots.txt blocks 2 AI answer engine crawlers
2 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
3 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,125 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://cumming-group.com/llms.txt (8 KiB, 50 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
https://cumming-group.com/en and / all use the title “Cumming Group | Project Management and Cost Consulting”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://cumming-group.com/en/services/planning-scheduling, https://cumming-group.com/en/services/digital-solutions, https://cumming-group.com/en/services/dispute-resolution-avoidance and https://cumming-group.com/en/services/energy-sustainability-solutions have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://cumming-group.com/en/about-us and https://cumming-group.com/en/about-us/affiliates use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is https://cumming-group.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 100 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
18 small tap targets
18 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
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.
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.
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 9-field form
Your longest form asks for 9 fields (7 required). Every extra field lowers completion.
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 731 words of copy
The homepage carries about 731 words of visible text.
2 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Learn More” and “Contact”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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 lehrercumming.com, 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 Tag Manager
- Hosting
- DigitalOcean
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on lehrercumming.com, including 15 speed issues, 2 SEO issues and 6 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.