Website review, no card needed

aosmd.com logo

aosmd.com website review

Visit site (opens in a new tab)Reviewed 29 October 202642 issues · 83 checks

This review found 42 issues worth fixing on aosmd.com, 11 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.9 s2.2 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.7 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.3 s
Jul 11, 20262.4 s
Jul 18, 20262.5 s
Jul 25, 20262.6 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
130 ms98 msMay 9Oct 24108 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026110 ms
May 16, 2026116 ms
May 23, 2026114 ms
May 30, 2026112 ms
Jun 6, 2026102 ms
Jun 13, 2026104 ms
Jun 20, 2026102 ms
Jun 27, 2026112 ms
Jul 4, 2026126 ms
Jul 11, 2026123 ms
Jul 18, 2026123 ms
Jul 25, 2026117 ms
Aug 1, 2026111 ms
Aug 8, 2026111 ms
Aug 15, 2026103 ms
Aug 22, 2026111 ms
Aug 29, 2026111 ms
Sep 5, 2026113 ms
Sep 12, 2026119 ms
Sep 19, 2026117 ms
Sep 26, 2026117 ms
Oct 3, 2026112 ms
Oct 10, 2026114 ms
Oct 17, 2026111 ms
Oct 24, 2026108 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

Full-page screenshot of aosmd.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aosmd.com at 0.4 s0.4 s
  2. aosmd.com at 0.8 s0.8 s
  3. aosmd.com at 1.1 s1.1 s
  4. aosmd.com at 1.5 s1.5 s
  5. aosmd.com at 1.9 s1.9 s
  6. aosmd.com at 2.3 s2.3 s
  7. aosmd.com at 2.6 s2.6 s
  8. aosmd.com at 3.0 s3.0 s

Speed

6 to fix71
  • Reduce unused JavaScript

    1.6 s · 350 KiB

    About 350 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Use efficient cache lifetimes

    3.3 MB

    4 files are served with short cache lifetimes, so returning visitors download them again (3.3 MB).

  • Improve image delivery

    3.2 MB

    4 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    300 ms · 19 KiB

    About 19 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Render-blocking requests

    300 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Legacy JavaScript

    150 ms · 25 KiB

    Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Google Fonts), adding 287 KiB and 75 ms of main-thread time.

  • 5 long tasks on the main thread

    5 long tasks block the main thread while loading, the longest for 99 ms. During a long task the page ignores taps.

  • 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: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 383 ms of it running JavaScript. That is comfortably low.

  • Server response: 41 ms

    41 ms

    Your server sent the HTML in 41 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • 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.

  • Largest Contentful Paint: 16.2 s

    16.2 s

    Your largest element takes 16.2 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 to colle…”.

  • Time to Interactive: 17.1 s

    17.1 s

    The page becomes fully interactive after 17.1 s. Good is under 3.8 s.

  • Real-user LCP: 2.9 s

    2.9 s

    Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user TTFB: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.4 s

    2.4 s

    The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image 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-24, real Chrome visitors' tap response (inp) went from 110 ms to 108 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-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user INP: 121 ms

    121 ms

    Real visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 50 ms

    50 ms

    Scripts block the page for only 50 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix25
  • Page weight: 4.3 MB in 42 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 42 requests on a phone: images 3.3 MB (8), scripts 771 KiB (19) and fonts 137 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    1.8 MB

    4 images are downloaded at several times the size a phone draws them, for example aos_hero_computing_power-stage-solutions.png at 1,755 px wide, shown at 390 px. Resized copies would save about 1.8 MB.

  • 4 images in older formats

    4 images (3.3 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.

  • About 1.2 g of CO₂ per visit

    1.21 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fixGoogle 8389
  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 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.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (27 elements)

    All page content should be contained by landmarks: 27 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.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h4 → h6, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 8372
  • Title is short (16 characters)

    Your title is only 16 characters: “AOS Home | AOSMD”. 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.

  • 6 H1 headlines

    There are 6 <h1> headlines (“Robust, High Performance IGBTs”, “Power Stage Solutions” and “1200V SiC MOSFETs”). One clear main headline is easier for people and search engines.

  • Meta description is long (234 characters)

    Your meta description is 234 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No robots.txt

    There is no robots.txt at aosmd.com/robots.txt, the first file search crawlers ask for.

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 67 internal links, 10 external

    The homepage links to 67 pages on aosmd.com and 10 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.aosmd.com/aos-home.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aosmd.com/sitemap.xml.

AI search readiness

1 to fix81
  • 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.aosmd.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
  • Text is in the HTML

    Your server sends the page's text in the HTML (390 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix70
  • 1 linked page hidden from search

    https://www.aosmd.com/news/alpha-and-omega-semiconductors-new-amos-e2-600v-super-junction-mosfets-support-optimized 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.aosmd.com/zh all use the title “AOS Home | AOSMD”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.aosmd.com/contact-us, https://www.aosmd.com/news/alpha-and-omega-semiconductors-new-amos-e2-600v-super-junction-mosfets-support-optimized, https://www.aosmd.com/application/automotive, https://www.aosmd.com/application/cloud, https://www.aosmd.com/application/computing and https://www.aosmd.com/application/consumer and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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.aosmd.com/zh, whose canonical is https://www.aosmd.com/zh/aos-home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 12 pages without an H1

    https://www.aosmd.com/contact-us, https://www.aosmd.com/application/automotive, https://www.aosmd.com/application/automotive/ev-powertrain, https://www.aosmd.com/application/cloud, https://www.aosmd.com/application/cloud/server and https://www.aosmd.com/application/cloud/telecom-infrastructure and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.aosmd.com/zh 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 28 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

    8 of 29 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 “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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.

  • 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 307 words of copy

    The homepage carries about 307 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “Learn More”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “CONTACT US”, “Learn More” and “Contact Us”.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • 4 other companies contacted

    Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 aosmd.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
Drupal
Framework
Next.js
Hosting
Imperva

Company

Employees
789
Founded
2000
Headquarters
Sunnyvale

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on aosmd.com, including 13 speed issues, 7 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25