Website review, no card needed
lmkr.com website review
Visit site (opens in a new tab)Reviewed 17 November 202637 issues · 68 checks
This review found 37 issues worth fixing on lmkr.com, 16 of them high impact, across 68 checks. The most urgent: reduce unused JavaScript. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 6.1 s |
| Jun 6, 2026 | 5.5 s |
| Jun 13, 2026 | 6.3 s |
| Jun 20, 2026 | 6.3 s |
| Jun 27, 2026 | 6.3 s |
| Jul 4, 2026 | 6.4 s |
| Jul 11, 2026 | 6.0 s |
| Jul 18, 2026 | 5.9 s |
| Jul 25, 2026 | 5.2 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 5.3 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.6 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.4 s |
| Sep 26, 2026 | 5.3 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 5.2 s |
| Oct 17, 2026 | 5.4 s |
| Oct 24, 2026 | 5.6 s |
| Oct 31, 2026 | 5.8 s |
| Nov 7, 2026 | 6.0 s |
| Nov 14, 2026 | 6.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 189 ms |
| Jun 20, 2026 | 198 ms |
| Jun 27, 2026 | 202 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 172 ms |
| Jul 25, 2026 | 148 ms |
| Aug 1, 2026 | 172 ms |
| Aug 8, 2026 | 188 ms |
| Aug 15, 2026 | 202 ms |
| Aug 22, 2026 | 229 ms |
| Aug 29, 2026 | 211 ms |
| Sep 5, 2026 | 200 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 174 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 174 ms |
| Oct 24, 2026 | 184 ms |
| Oct 31, 2026 | 179 ms |
| Nov 7, 2026 | 202 ms |
| Nov 14, 2026 | 206 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
Reduce unused JavaScript
2.8 s · 568 KiBAbout 568 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
4 third-party services on the page
4 third-party services load with your homepage (Clarity, Google Tag Manager and oraclecloud.com and others), adding 17.1 MB and 385 ms of main-thread time.
oraclecloud.com adds 3 ms
3 msoraclecloud.com costs a phone 3 ms of main-thread work and 16.9 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 57
57/100Your mobile performance score is 57. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
500 ms · 159 KiB4 images could be 159 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Clarity adds 287 ms
287 msClarity costs a phone 287 ms of main-thread work and 28 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
50 ms · 197 KiB2 files are served with short cache lifetimes, so returning visitors download them again (197 KiB).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 104 ms. During a long task the page ignores taps.
Minify JavaScript
8 KiB8 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.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 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 LCP: 6.1 s
6.1 sReal visitors wait 6.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.0 s
5.0 sReal visitors see the first content after 5.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 14.1 s
14.1 sVisually, the page fills in at 14.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.2 s
13.2 sThe page becomes fully interactive after 13.2 s. Good is under 3.8 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user INP: 217 ms
217 msReal visitors wait 217 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
Tap response (INP) got 36% slower for real visitors
+36%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 153 ms to 206 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 6.1 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Cumulative Layout Shift: 0.087
0.087The layout barely moves while loading (CLS 0.087, good is under 0.1).
Total Blocking Time: 86 ms
86 msScripts block the page for only 86 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 18.7 MB in 56 requests
18.7 MBYour homepage downloads 18.7 MB in 56 requests on a phone: other files 16.8 MB (32), scripts 1.1 MB (10) and images 733 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 5.3 g of CO₂ per visit
5.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.30 g of CO₂e: 635.8 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 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.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
4 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Transform disconnected data into connected digital ecosystems. LMKR delivers advanced geoscience, urban mobility, and A…”.
Title: 52 characters
Your title is a healthy 52 characters: “Digital Transformation for Complex Industries | LMKR”.
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://lmkr.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 226 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
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.
llms.txt published
The site publishes https://lmkr.com/llms.txt (8 KiB, 30 links), a plain-text guide to the site for AI tools.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Loading the image 'https://c.clarity.ms/c.gif' violates the following Content Security Policy directive: "img-src 'self…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 226 words
The homepage has only about 226 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get in Touch”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
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 lmkr.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Oracle Cloud
Hiring
- Hiring
- 3 open roles
- Teams
- IT (2), Sales (1)
- Job board
- bamboohr
- Careers page
- lmkr.bamboohr.com/careers (opens in a new tab)
Company
- Employees
- 27
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on lmkr.com, including 20 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.