Website review, no card needed
lumexaimaging.com website review
Visit site (opens in a new tab)Reviewed 3 November 202631 issues · 81 checks
This review found 31 issues worth fixing on lumexaimaging.com, 7 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 86 ms |
| May 23, 2026 | 86 ms |
| May 30, 2026 | 85 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 82 ms |
| Jun 20, 2026 | 88 ms |
| Jun 27, 2026 | 91 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 93 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 83 ms |
| Aug 22, 2026 | 79 ms |
| Aug 29, 2026 | 80 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 85 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 89 ms |
| Oct 3, 2026 | 89 ms |
| Oct 10, 2026 | 90 ms |
| Oct 17, 2026 | 91 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 89 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
Render-blocking requests
1.5 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
1,864 HTML elements
The page has 1,864 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
165 KiBAbout 165 KiB of JavaScript is downloaded but never used on this page.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, userway.org and oursprivacy.com and others), adding 400 KiB and 116 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.
Improve image delivery
36 KiB1 image could be 36 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
24 KiB3 files are served with short cache lifetimes, so returning visitors download them again (24 KiB).
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 341 ms of it running JavaScript. That is comfortably low.
Server response: 120 ms
120 msYour server sent the HTML in 120 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: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 836 ms
836 msReal visitors wait 836 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shaping the Future of Imaging”.
Time to Interactive: 6.8 s
6.8 sThe page becomes fully interactive after 6.8 s. Good is under 3.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
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 86 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Total Blocking Time: 11 ms
11 msScripts block the page for only 11 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 82 requests
3.4 MBYour homepage downloads 3.4 MB in 82 requests on a phone: media 1.9 MB (1), HTML 514 KiB (1) and scripts 462 KiB (26). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (208 KiB) is 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.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 114.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
7 buttons without a name
7 buttons have no accessible name, so screen readers announce just “button”.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (17 elements)
All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (306 characters)
Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.
40 internal links, 4 external
The homepage links to 40 pages on lumexaimaging.com and 4 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Shaping the Future of Imaging”.
Title: 46 characters
Your title is a healthy 46 characters: “Lumexa Imaging • Shaping the Future of Imaging”.
Canonical URL set
The canonical URL is https://www.lumexaimaging.com/.
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://www.lumexaimaging.com/sitemap_index.xml.
AI search readiness
Some text only appears after JavaScript runs
46%The HTML your server sends has 170 of the 372 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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://www.lumexaimaging.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.
1 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.
Other pages
2 pages without a meta description
https://www.lumexaimaging.com/connexia/connexia-leadership and https://www.lumexaimaging.com/connexia/providers have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.lumexaimaging.com/our-brands and https://www.lumexaimaging.com/stronger-together 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 https://www.lumexaimaging.com/connexia/providers, whose canonical is https://www.lumexaimaging.com/providers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.lumexaimaging.com/connexia, https://www.lumexaimaging.com/connexia/our-services, https://www.lumexaimaging.com/connexia/connexia-leadership and https://www.lumexaimaging.com/connexia/providers have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.lumexaimaging.com/our-brands 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 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.
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 15 pages that loaded have a <title>.
Best practices
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”.
2 checks passed
Tap targets are thumb-sized
39 of 43 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 372 words of copy
The homepage carries about 372 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 IN TOUCH”.
2 calls to action
The homepage has 2 calls to action, for example “Get in Touch”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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.
4 cookies set on arrival
4Opening 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 lumexaimaging.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
- WP Engine
Hiring
- Hiring
- 11 open roles
- Teams
- Body Imaging: Daytime (3), Body Imaging: Overnight (3), Neuroradiology Overnight (2), Neuroradiology Daytime (1)
- Job board
- lever
Company
- Employees
- 5,037
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on lumexaimaging.com, including 11 speed issues, 1 SEO issue and 1 conversion gap. 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.