Website review, no card needed
ams-osram.com website review
Visit site (opens in a new tab)Reviewed 20 October 202638 issues · 78 checks
This review found 38 issues worth fixing on ams-osram.com, 14 of them high impact, across 78 checks. The most urgent: page weight: 27.9 MB in 173 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
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.0 s |
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.3 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 132 ms |
| May 9, 2026 | 133 ms |
| May 16, 2026 | 132 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 137 ms |
| Jun 6, 2026 | 141 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 151 ms |
| Jul 4, 2026 | 148 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 140 ms |
| Jul 25, 2026 | 131 ms |
| Aug 1, 2026 | 129 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 132 ms |
| Aug 29, 2026 | 133 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 133 ms |
| Sep 19, 2026 | 135 ms |
| Sep 26, 2026 | 131 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 129 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.0 s · 375 KiBAbout 375 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
2.1 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 84). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
600 ms · 21.1 MB35 files are served with short cache lifetimes, so returning visitors download them again (21.1 MB).
Improve image delivery
1.4 MB13 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
890 ms · 138 KiBAbout 138 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 890 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and leadinfo.com), adding 437 KiB and 753 ms of main-thread time.
Usercentrics CMP adds 560 ms
560 msUsercentrics CMP costs a phone 560 ms of main-thread work and 259 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 353 ms. During a long task the page ignores taps.
2,323 HTML elements
The page has 2,323 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 84 but mobile only 45. 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.
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: 123 ms
123 msYour server sent the HTML in 123 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: 5.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 14.7 s
14.7 sYour largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AI Photonics – creating the optical interconnects of tomorr…”.
Time to Interactive: 16.5 s
16.5 sThe page becomes fully interactive after 16.5 s. Good is under 3.8 s.
Speed Index: 10.2 s
10.2 sVisually, the page fills in at 10.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 595 ms
595 msScripts block taps and scrolling for 595 ms in total while the page loads. Good is under 200 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 132 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 166 ms
166 msReal visitors wait 166 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 27.9 MB in 173 requests
27.9 MBYour homepage downloads 27.9 MB in 173 requests on a phone: media 24.4 MB (12), scripts 1.6 MB (113) and images 1.5 MB (18). Under 2 MB keeps phones on slow connections fast.
About 7.9 g of CO₂ per visit
7.92 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.92 g of CO₂e: 950.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (81 characters)
Your title is 81 characters, so Google will cut it off around 60: “ams OSRAM is a global leader in innovative light and sensor solutions | ams OSRAM”.
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 (245 characters)
Your meta description is 245 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://ams-osram.com/sitemap.xml, so Google discovers your pages only by following links.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
237 internal links, 12 external
The homepage links to 237 pages on ams-osram.com and 12 external pages.
4 checks passed
One H1 headline
Your main headline reads: “ams OSRAM is a global leader in innovative light and sensor solutions”.
Canonical URL set
The canonical URL is https://ams-osram.com/.
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.
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://ams-osram.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 (2,219 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://ams-osram.com/products/drivers and https://ams-osram.com/products/drivers/led-drivers all use the title “LED Drivers | ams OSRAM”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://ams-osram.com/products/drivers and https://ams-osram.com/products/drivers/led-drivers use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://ams-osram.com/products/product-selector, whose canonical is https://ams-osram.com/search?productSearch=true. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://ams-osram.com/products/product-selector has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 174 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 a meta description
All 15 pages that loaded have a meta description.
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
16 of 18 tappable elements near the top are at least 24 px.
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.
About 1,852 words of copy
The homepage carries about 1,852 words of visible text.
6 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Download center” and “Subscribe”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and “more than 20,000 customers”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
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). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
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 ams-osram.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Tag Manager
Company
- Founded
- 1919
- Headquarters
- Munich
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 ams-osram.com, including 21 speed issues, 5 SEO issues 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.