apc.com website review

78 files are served with short cache lifetimes, so returning visitors download them again (790 KiB).

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

Your mobile performance score is 28 (desktop: 33). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 8.7 s on main-thread work while loading, 5.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 3,807 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

17 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Dynatrace, Google Tag Manager and VWO and others), adding 852 KiB and 1.2 s of main-thread time.

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

94 KiB could be saved by minifying JavaScript.

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

Dynatrace costs a phone 468 ms of main-thread work and 144 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.

Google Tag Manager costs a phone 294 ms of main-thread work and 197 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.

39 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

1 image could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 5.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.

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

Scripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.

Your homepage downloads 3.5 MB in 745 requests on a phone: scripts 2.6 MB (517), other files 297 KiB (157) and images 254 KiB (9). Under 2 MB keeps phones on slow connections fast.

1 image (63 KiB) is 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.

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

Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

Your title is 69 characters, so Google will cut it off around 60: “Get to know the full range of APC Branded offers | Schneider Electric”.

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

12 links have no real href, so search engines can't follow them.

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

The homepage links to 118 pages on apc.com and 9 external pages.

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.

There is no /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.

/ww/en/product-subcategory/8010-home-office-electronics, /ww/en/product-subcategory/8020-network-and-server, /ww/en/product-subcategory/7510-racks-and-enclosures and /ww/en/product-subcategory/7410-rack-power-distribution are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ww/en/product-subcategory/8010-home-office-electronics, /ww/en/product-subcategory/8020-network-and-server, /ww/en/product-subcategory/7510-racks-and-enclosures and /ww/en/product-subcategory/7410-rack-power-distribution all use the title “Country Selector | Schneider Electric Global”. Search engines can't tell which page to show for a search, so each competes with the others.

/ww/en/product-subcategory/8010-home-office-electronics, /ww/en/product-subcategory/8020-network-and-server, /ww/en/product-subcategory/7510-racks-and-enclosures and /ww/en/product-subcategory/7410-rack-power-distribution use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /ww/en/work/solutions/for-business/data-centers-and-networks/micro, whose canonical is /ww/en/work/solutions/data-centers-and-networks/micro. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/ww/en/product-subcategory/8010-home-office-electronics, /ww/en/product-subcategory/8020-network-and-server, /ww/en/product-subcategory/7510-racks-and-enclosures and /ww/en/product-subcategory/7410-rack-power-distribution have no <h1> headline, so visitors and search engines get no clear main topic.

/ww/en/about-us/open-source, /ww/en/about-us/university, /ww/en/work/solutions, /ww/en/work/software and /ww/en/work/services/spare-parts-management have 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.

/ww/en/about-us/university, /ww/en/product-subcategory/8020-network-and-server and /ww/en/work/solutions/edge-computing took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Content security policy”).

Opening https://apc.com goes through 4 redirects before the homepage loads.

2 links go through two or more redirects, for example https://www.apc.com/shop/ww/en/warranty/product-registration.jsp.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

se.com is registered until Oct 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

se.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 232 words of visible text; thin pages give Google and first-time buyers little to go on.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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