Website review, no card needed

wago.com logo

wago.com website review

Visit site (opens in a new tab)Reviewed 1 November 202628 issues · 77 checks

This review found 28 issues worth fixing on wago.com, 7 of them high impact, across 77 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.8 s1.8 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.3 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.7 s
Sep 12, 20262.6 s
Sep 19, 20262.4 s
Sep 26, 20262.2 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
184 ms139 msMay 9Oct 24179 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026145 ms
May 23, 2026144 ms
May 30, 2026144 ms
Jun 6, 2026144 ms
Jun 13, 2026145 ms
Jun 20, 2026144 ms
Jun 27, 2026145 ms
Jul 4, 2026145 ms
Jul 11, 2026145 ms
Jul 18, 2026146 ms
Jul 25, 2026146 ms
Aug 1, 2026145 ms
Aug 8, 2026147 ms
Aug 15, 2026151 ms
Aug 22, 2026154 ms
Aug 29, 2026161 ms
Sep 5, 2026166 ms
Sep 12, 2026170 ms
Sep 19, 2026174 ms
Sep 26, 2026176 ms
Oct 3, 2026174 ms
Oct 10, 2026175 ms
Oct 17, 2026175 ms
Oct 24, 2026179 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 wago.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix53
  • Reduce unused JavaScript

    1.8 s · 334 KiB

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

  • Use efficient cache lifetimes

    900 ms · 283 KiB

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

  • Mobile performance score: 53

    53/100

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

  • Render-blocking requests

    600 ms

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

  • Main-thread work: 3.2 s

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

  • 9 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Gigya and Usercentrics CMP and others), adding 826 KiB and 379 ms of main-thread time.

  • Improve image delivery

    44 KiB

    2 images could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    28 KiB

    About 28 KiB of CSS is downloaded but never applied on this page.

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

1 checks passed
  • Server response: 401 ms

    401 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use third-party website tracking technologies to provide…”.

  • Time to Interactive: 12.0 s

    12.0 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • Total Blocking Time: 648 ms

    648 ms

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

  • Tap response (INP) got 22% slower for real visitors

    +22%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 146 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 486 ms

    486 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    83bfafd5d4b843ef817dfa3eeafacc41 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).

  • 1 image in older formats

    1 image (36 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.

  • About 0.5 g of CO₂ per visit

    0.51 g

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

2 checks passed
  • Page weight: 1.8 MB in 150 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 150 requests on a phone: scripts 987 KiB (59), images 308 KiB (22) and other files 191 KiB (57). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9596
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

5 to fixGoogle 9280
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “WAGO USA | Revolutionizing Automation, Interconnections, and Interface | WAGO”.

  • Meta description is long (252 characters)

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

  • No XML sitemap

    No XML sitemap at https://www.wago.com/sitemap.xml, so Google discovers your pages only by following links.

  • 7 links with vague text

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

  • 28 internal links, 10 external

    The homepage links to 28 pages on wago.com and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Homepage”.

  • Canonical URL set

    The canonical URL is https://www.wago.com/us/.

  • Structured data in place

    Structured data found: BreadcrumbList and Corporation.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.wago.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.

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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

5 to fix67
  • 1 page without a title

    https://www.wago.com/us/comparisonlist has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.wago.com/us/comparisonlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.wago.com/us/comparisonlist and https://www.wago.com/us/software/plc-agent have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.wago.com/us/products/general/app and https://www.wago.com/us/products/electrical-interconnect use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.wago.com/us/careers, https://www.wago.com/us/comparisonlist, https://www.wago.com/us/crossreferences and https://www.wago.com/us/distribution have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.wago.com/us/products/general/app and https://www.wago.com/us/crossreferences 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.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    15 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 344 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact”, “WHERE TO BUY” and “Learn More”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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 (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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 wago.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
Nuxt
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on wago.com, including 11 speed issues, 5 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

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