Website review, no card needed
squared.com website review
Visit site (opens in a new tab)Reviewed 17 November 202644 issues · 94 checks
This review found 44 issues worth fixing on squared.com, 23 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. 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) |
|---|---|
| May 30, 2026 | 5.5 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 5.2 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 4.0 s |
| Oct 31, 2026 | 3.9 s |
| Nov 7, 2026 | 3.8 s |
| Nov 14, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 682 ms |
| Jun 6, 2026 | 670 ms |
| Jun 13, 2026 | 620 ms |
| Jun 20, 2026 | 584 ms |
| Jun 27, 2026 | 566 ms |
| Jul 4, 2026 | 556 ms |
| Jul 11, 2026 | 571 ms |
| Jul 18, 2026 | 583 ms |
| Jul 25, 2026 | 589 ms |
| Aug 1, 2026 | 595 ms |
| Aug 8, 2026 | 606 ms |
| Aug 15, 2026 | 618 ms |
| Aug 22, 2026 | 626 ms |
| Aug 29, 2026 | 640 ms |
| Sep 5, 2026 | 651 ms |
| Sep 12, 2026 | 660 ms |
| Sep 19, 2026 | 662 ms |
| Sep 26, 2026 | 640 ms |
| Oct 3, 2026 | 618 ms |
| Oct 10, 2026 | 597 ms |
| Oct 17, 2026 | 586 ms |
| Oct 24, 2026 | 584 ms |
| Oct 31, 2026 | 578 ms |
| Nov 7, 2026 | 563 ms |
| Nov 14, 2026 | 568 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
Use efficient cache lifetimes
1.8 s · 706 KiB76 files are served with short cache lifetimes, so returning visitors download them again (706 KiB).
Reduce unused JavaScript
1.4 s · 547 KiBAbout 547 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.4 s35 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 6.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,429 HTML elements
The page has 5,429 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
800 ms · 2.4 MB19 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Dynatrace, Google Tag Manager and VWO and others), adding 822 KiB and 1.3 s of main-thread time.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.
Dynatrace adds 486 ms
486 msDynatrace costs a phone 486 ms of main-thread work and 148 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.
Reduce unused CSS
300 ms · 76 KiBAbout 76 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.
Google Tag Manager adds 271 ms
271 msGoogle Tag Manager costs a phone 271 ms of main-thread work and 196 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.
VWO adds 257 ms
257 msVWO costs a phone 257 ms of main-thread work and 184 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.
Duplicated JavaScript
150 ms · 39 KiB39 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
98 KiB98 KiB could be saved by minifying JavaScript.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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: 66 ms
66 msYour server sent the HTML in 66 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 INP: 603 ms
603 msReal visitors wait 603 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 20.5 s
20.5 sYour largest element takes 20.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 27.8 s
27.8 sThe page becomes fully interactive after 27.8 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
7 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 635 ms
635 msReal visitors wait 635 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 682 ms to 568 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.5 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 776 requests
6.0 MBYour homepage downloads 6.0 MB in 776 requests on a phone: images 2.8 MB (30), scripts 2.5 MB (471) and other files 276 KiB (218). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
683 KiB3 images are downloaded at several times the size a phone draws them, for example 1138253795-1080x1080.jpg at 1,080 px wide, shown at 240 px. Resized copies would save about 683 KiB.
5 images in older formats
5 images (1.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.
1 image below the first screen load straight away
1 image further down the page (72 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.70 g of CO₂e: 204.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (5 elements)
Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
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.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links must have discernible text (1 element)
Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (198 characters)
Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.
15 links crawlers can't follow
15 links have no real href, so search engines can't follow them.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
100 internal links, 8 external
The homepage links to 100 pages on squared.com and 8 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Square D™ by Schneider Electric”.
Title: 43 characters
Your title is a healthy 43 characters: “Square D | Schneider Electric United States”.
Canonical URL set
The canonical URL is https://www.se.com/us/en/brands/squared/.
Structured data in place
Structured data found: BreadcrumbList and WebPage.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.se.com/ae/en/download/sitemapindex/.
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.se.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 (549 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.se.com/us/en/download/mylist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.se.com/us/en/product-cart has 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.se.com/us/en/work/support, whose canonical is https://www.se.com/us/en/work/help. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.se.com/us/en/download/mylist, https://www.se.com/us/en/product-cart and https://www.se.com/us/en/all-products have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages with very little text
https://www.se.com/us/en/brands/apc, https://www.se.com/us/en/product-cart, https://www.se.com/us/en/home, https://www.se.com/us/en/all-products, https://www.se.com/us/en/work/software and https://www.se.com/us/en/work/services and 6 others 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.
2 pages slow to respond
https://www.se.com/us/en/product-cart and https://www.se.com/us/en/work/support took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 66 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.
Titles are unique
Every page we checked has its own title.
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: the server responded with a status of 429 ()”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
10 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 545 words of copy
The homepage carries about 545 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Where to Buy”.
4 calls to action
The homepage has 4 calls to action, for example “Where to Buy”, “Learn more Meet the new QO™ breakers” and “Where to buy”.
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).
15 other companies contacted
Loading the homepage contacts 15 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 squared.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
- SvelteKit
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on squared.com, including 20 speed issues, 3 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.