Website review, no card needed
advancedenergy.com website review
Visit site (opens in a new tab)Reviewed 19 October 202647 issues · 88 checks
This review found 47 issues worth fixing on advancedenergy.com, 21 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.0 s |
| May 2, 2026 | 3.0 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 150 ms |
| May 2, 2026 | 155 ms |
| May 9, 2026 | 155 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 150 ms |
| Jul 25, 2026 | 150 ms |
| Aug 1, 2026 | 149 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 152 ms |
| Sep 5, 2026 | 152 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 160 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 162 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.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
Improve image delivery
19.2 s · 5.4 MB15 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 19.2 s faster on a phone.
Reduce unused JavaScript
3.5 s · 683 KiBAbout 683 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 378 KiB18 files are served with short cache lifetimes, so returning visitors download them again (378 KiB).
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.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 69). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and azure.com and others), adding 1.9 MB and 372 ms of main-thread time.
Reduce unused CSS
300 ms · 87 KiBAbout 87 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.
1,562 HTML elements
The page has 1,562 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
site.com adds 42 ms
42 mssite.com costs a phone 42 ms of main-thread work and 750 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.
JSDelivr CDN adds 0 ms
0 msJSDelivr CDN costs a phone 0 ms of main-thread work and 587 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Legacy JavaScript
200 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 91 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 663 ms of it running JavaScript. That is comfortably low.
Server response: 64 ms
64 msYour server sent the HTML in 64 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: 4.0 s
4.0 sReal visitors wait 4.0 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: 38.7 s
38.7 sYour largest element takes 38.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MDN”.
Time to Interactive: 39.1 s
39.1 sThe page becomes fully interactive after 39.1 s. Good is under 3.8 s.
Speed Index: 13.6 s
13.6 sVisually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 150 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 198 ms
198 msReal visitors wait 198 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).
Total Blocking Time: 61 ms
61 msScripts block the page for only 61 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.6 MB in 71 requests
8.6 MBYour homepage downloads 8.6 MB in 71 requests on a phone: images 6.0 MB (22), scripts 1.6 MB (21) and other files 709 KiB (16). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
3.3 MB2 images are downloaded at several times the size a phone draws them, for example hero_Centra-Smarthub_4-2.jpg at 2,800 px wide, shown at 390 px. Resized copies would save about 3.3 MB.
12 images in older formats
12 images (5.8 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.
An image on the first screen is lazy-loaded
CSU-NPI-Homepage-Banner.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images below the first screen load straight away
4 images further down the page (797 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.44 g of CO₂e: 293.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (8 elements).
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
49 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: 49 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (22 characters)
Your title is only 22 characters: “Home | Advanced Energy”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
306 internal links, 24 external
The homepage links to 306 pages on advancedenergy.com and 24 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Home”.
Canonical URL set
The canonical URL is https://www.advancedenergy.com/en-us/.
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.advancedenergy.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.
3 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 (1,613 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.advancedenergy.com/llms.txt (1 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.advancedenergy.com/en-us/contact-us-form has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.advancedenergy.com/en-us/contact-us-form is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
12 pages without a meta description
https://www.advancedenergy.com/en-us/about/acquired-technologies, https://www.advancedenergy.com/en-us/about/working-at-advanced-energy, https://www.advancedenergy.com/en-us/safety-and-compliance, https://www.advancedenergy.com/en-us/about/news, https://www.advancedenergy.com/en-us/about/news/blog and https://www.advancedenergy.com/en-us/about/news/press and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.advancedenergy.com/en-us/contact-us-form 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 199 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Best practices
12 small tap targets
12 of 54 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'error')”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 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 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 874 words of copy
The homepage carries about 874 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: “Shop Online” and “How to Buy”.
25 calls to action
The homepage has 25 calls to action, for example “How to Buy”, “Contact Us” and “My Order History”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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 (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 advancedenergy.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
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on advancedenergy.com, including 19 speed issues, 6 SEO issues and 2 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.