Website review, no card needed

amadaweldtech.com logo

amadaweldtech.com website review

Visit site (opens in a new tab)Reviewed 19 October 202642 issues · 88 checks

This review found 42 issues worth fixing on amadaweldtech.com, 17 of them high impact, across 88 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
3.2 s1.8 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.7 s
May 9, 20262.7 s
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.7 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20262.8 s
Jul 25, 20262.5 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.7 s
Oct 3, 20262.5 s
Oct 10, 20262.6 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
124 ms75 msMay 2Oct 17100 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202689 ms
May 9, 202687 ms
May 16, 202686 ms
May 23, 202686 ms
May 30, 202683 ms
Jun 6, 202683 ms
Jun 13, 202681 ms
Jun 20, 202682 ms
Jun 27, 202685 ms
Jul 4, 202690 ms
Jul 11, 202697 ms
Jul 18, 2026118 ms
Jul 25, 2026114 ms
Aug 1, 202690 ms
Aug 8, 202690 ms
Aug 15, 202686 ms
Aug 22, 202684 ms
Aug 29, 202690 ms
Sep 5, 202688 ms
Sep 12, 202693 ms
Sep 19, 202693 ms
Sep 26, 202695 ms
Oct 3, 202693 ms
Oct 10, 202693 ms
Oct 17, 2026100 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 amadaweldtech.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amadaweldtech.com at 0.8 s0.8 s
  2. amadaweldtech.com at 1.6 s1.6 s
  3. amadaweldtech.com at 2.3 s2.3 s
  4. amadaweldtech.com at 3.1 s3.1 s
  5. amadaweldtech.com at 3.9 s3.9 s
  6. amadaweldtech.com at 4.7 s4.7 s
  7. amadaweldtech.com at 5.5 s5.5 s
  8. amadaweldtech.com at 6.2 s6.2 s

Speed

9 to fix39
  • Reduce unused JavaScript

    5.3 s · 658 KiB

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

  • Render-blocking requests

    1.5 s

    22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.

  • Mobile performance score: 39

    39/100

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

  • Improve image delivery

    750 ms · 4.8 MB

    9 images could be 4.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.4 MB and 1.3 s of main-thread time.

  • Reduce unused CSS

    910 ms · 103 KiB

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

  • Google CDN adds 474 ms

    474 ms

    Google CDN costs a phone 474 ms of main-thread work and 733 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.

  • Main-thread work: 3.9 s

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

  • 2,106 HTML elements

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

  • 20 long tasks on the main thread

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

  • Minify CSS

    150 ms · 11 KiB

    11 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    123 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 69 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

11 to fix0
  • 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.

  • First Contentful Paint: 8.3 s

    8.3 s

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

  • Largest Contentful Paint: 28.5 s

    28.5 s

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

  • Time to Interactive: 30.0 s

    30.0 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user CLS: 0.11

    0.11

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 591 ms

    591 ms

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

  • Cumulative Layout Shift: 0.1

    0.1

    The layout shifts by 0.1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

Images and page weight

4 to fix25
  • Page weight: 8.2 MB in 139 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 139 requests on a phone: images 6.1 MB (68), scripts 1.4 MB (37) and other files 358 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    WL-300A-Web-Banner.gif weighs 4.5 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    3.2 MB

    4 images are downloaded at several times the size a phone draws them, for example WL-300A-Web-Banner.gif at 2,000 px wide, shown at 390 px. Resized copies would save about 3.2 MB.

  • 1 image in older formats

    1 image (4.5 MB) 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.

  • 1 image below the first screen load straight away

    1 image further down the page (65 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.3 g of CO₂ per visit

    2.31 g

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

Accessibility

10 to fixGoogle 8086
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails 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.

  • 2 form fields without a label

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

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

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 8588
  • 38 links crawlers can't follow

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • One H1 headline

    Your <h1> is empty.

  • 278 internal links, 8 external

    The homepage links to 278 pages on amadaweldtech.com and 8 external pages.

6 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Manufacturer of equipment and systems for welding, cutting, marking, micromachining, sealing, and bonding. Resistance w…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Equipment & Systems | Weld - Mark - Cut | AMADA WELD TECH”.

  • Canonical URL set

    The canonical URL is https://amadaweldtech.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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://amadaweldtech.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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,230 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://amadaweldtech.com/llms.txt (195 KiB, 1,178 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 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.

  • 20 distorted images

    20 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 456 words of copy

    The homepage carries about 456 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: “Contact Us” and “Learn more”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Quick Start Guides”, “Training Request” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

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

  • 17 cookies set on arrival

    17

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

  • 14 other companies contacted

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) 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 amadaweldtech.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

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 amadaweldtech.com, including 20 speed issues, 4 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

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