Website review, no card needed
lappgroup.com website review
Visit site (opens in a new tab)Reviewed 21 October 202638 issues · 85 checks
This review found 38 issues worth fixing on lappgroup.com, 11 of them high impact, across 85 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 114 ms |
| May 9, 2026 | 112 ms |
| May 16, 2026 | 114 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 132 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 93 ms |
| Aug 15, 2026 | 93 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 103 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 93 ms |
| Oct 17, 2026 | 92 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.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.8 s
Speed
Reduce unused JavaScript
1.1 s · 282 KiBAbout 282 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Use efficient cache lifetimes
1.0 s · 256 KiB28 files are served with short cache lifetimes, so returning visitors download them again (256 KiB).
Mobile performance score: 69
69/100Your mobile performance score is 69 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
700 ms · 63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 700 ms faster on a phone.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Reduce unused CSS
310 ms · 98 KiBAbout 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Render-blocking requests
350 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 246 ms. During a long task the page ignores taps.
3 third-party services on the page
3 third-party services load with your homepage (cookiepro.com, ecn-ldr.de and Optanon), adding 308 KiB and 165 ms of main-thread time.
Phones get a much slower page than desktops
Desktop scores 94 but mobile only 69. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 723 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies and similar technologies (hereina…”. Most of its time is element render delay (2.7 s).
Time to Interactive: 8.7 s
8.7 sThe page becomes fully interactive after 8.7 s. Good is under 3.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
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: 94 ms
94 msReal visitors wait 94 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 766 ms
766 msReal visitors wait 766 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 114 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 121 ms
121 msScripts block the page for only 121 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 43.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.3 MB in 41 requests
1.3 MBYour homepage downloads 1.3 MB in 41 requests on a phone: scripts 740 KiB (19), fonts 420 KiB (5) and stylesheets 80 KiB (2). That is a lean page.
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
15 elements use ARIA attributes their role does not allow, which confuses screen readers.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 7 failed. 3 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.
Title is short (10 characters)
Your title is only 10 characters: “Lapp Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (168 characters)
Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
11 internal links, 112 external
The homepage links to 11 pages on lappgroup.com and 112 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.lappgroup.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.lappgroup.com/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.lappgroup.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
1 linked page hidden from search
https://www.lappgroup.com/privacy-policy.html is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://www.lappgroup.com/de all use the title “Lapp Group”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages share a meta description
https://www.lappgroup.com/de, https://www.lappgroup.com/company/specialist-companies.html, https://www.lappgroup.com/privacy-policy.html, https://www.lappgroup.com/imprint.html and https://www.lappgroup.com/sitemap.html use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.lappgroup.com/de has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.lappgroup.com/sitemap.html 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.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 5 pages that loaded have a meta description.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
6 small tap targets
6 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 71 words
The homepage has only about 71 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
1 short form
A short form (0 fields at most) is right on the homepage.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 lappgroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on lappgroup.com, including 11 speed issues, 7 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.