Website review, no card needed
welding-alloys.com website review
Visit site (opens in a new tab)Reviewed 3 November 202632 issues · 82 checks
This review found 32 issues worth fixing on welding-alloys.com, 17 of them high impact, across 82 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
73C- #92,854 of 125,902 reviewed websitesbeats 23%
- #57,461 of 70,296 online storesbeats 15%
- #1,811 of 2,954 WooCommerce storesbeats 33%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 6.2 s |
| May 23, 2026 | 6.5 s |
| May 30, 2026 | 6.7 s |
| Jun 6, 2026 | 6.5 s |
| Jun 13, 2026 | 6.5 s |
| Jun 20, 2026 | 6.3 s |
| Jun 27, 2026 | 6.3 s |
| Jul 4, 2026 | 6.4 s |
| Jul 11, 2026 | 7.0 s |
| Jul 18, 2026 | 7.1 s |
| Jul 25, 2026 | 7.3 s |
| Aug 1, 2026 | 7.5 s |
| Aug 8, 2026 | 7.0 s |
| Aug 15, 2026 | 6.9 s |
| Aug 22, 2026 | 6.5 s |
| Aug 29, 2026 | 6.3 s |
| Sep 5, 2026 | 6.3 s |
| Sep 12, 2026 | 6.4 s |
| Sep 19, 2026 | 6.6 s |
| Sep 26, 2026 | 6.6 s |
| Oct 3, 2026 | 6.6 s |
| Oct 10, 2026 | 6.5 s |
| Oct 17, 2026 | 6.5 s |
| Oct 24, 2026 | 6.5 s |
| Oct 31, 2026 | 6.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 141 ms |
| May 23, 2026 | 140 ms |
| May 30, 2026 | 139 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 140 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 132 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 140 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 132 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 133 ms |
| Oct 10, 2026 | 134 ms |
| Oct 17, 2026 | 135 ms |
| Oct 24, 2026 | 140 ms |
| Oct 31, 2026 | 138 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
1.4 s
2.8 s
4.1 s
5.5 s
6.9 s
8.3 s
9.6 s
11.0 s
Speed
Use efficient cache lifetimes
3.5 s · 1.1 MB79 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Render-blocking requests
2.6 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Reduce unused JavaScript
1.9 s · 522 KiBAbout 522 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
900 ms · 249 KiBAbout 249 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Improve image delivery
300 ms · 504 KiB9 images could be 504 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (leadoo.com, siliconvalleybz.com and cdn-cookieyes.com and others), adding 1.2 MB and 318 ms of main-thread time.
Legacy JavaScript
350 ms · 53 KiBPolyfills for old browsers add 53 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
leadoo.com adds 181 ms
181 msleadoo.com costs a phone 181 ms of main-thread work and 1.0 MB 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.
2,194 HTML elements
The page has 2,194 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 69 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.
1 checks passed
Server response: 112 ms
112 msYour server sent the HTML in 112 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: 5.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.66
0.66For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.7 s
13.7 sYour largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 16.2 s
16.2 sThe page becomes fully interactive after 16.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.574
0.574The layout shifts by 0.574 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 141 ms to 138 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.2 s to 6.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 127 requests
3.4 MBYour homepage downloads 3.4 MB in 127 requests on a phone: images 1.3 MB (33), scripts 1.1 MB (28) and fonts 605 KiB (15). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (187 KiB) 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.
5 images below the first screen load straight away
5 images further down the page (278 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.95 g of CO₂e: 114.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
30 tap targets too small
30 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 51 images in the HTML carry an alt attribute.
47 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: 47 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
198 internal links, 6 external
The homepage links to 198 pages on welding-alloys.com and 6 external pages.
8 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Welding Alloys increases productivity and reduces costs through an extensive range of welding consumables, automated we…”.
One H1 headline
Your main headline reads: “Our products and services”.
Title: 48 characters
Your title is a healthy 48 characters: “Home: Our products and services | Welding Alloys”.
Canonical URL set
The canonical URL is https://www.welding-alloys.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.welding-alloys.com/sitemap_index.xml.
AI search readiness
4 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 (946 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.welding-alloys.com/llms.txt (9 KiB, 50 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.welding-alloys.com/request-a-quote is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages slow to respond
https://www.welding-alloys.com/request-a-quote, https://www.welding-alloys.com/es, https://www.welding-alloys.com/services/engineered-wear-services, https://www.welding-alloys.com/services/engineered-wear-services/application-methods and https://www.welding-alloys.com/services/engineered-wear-services/application-methods/cladding-applications took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 102 found) and read each the way a search engine does.
6 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 14 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.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
Thin social proof
Social proof on the homepage: 15 testimonial or review blocks. 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 533 words of copy
The homepage carries about 533 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: “View Quote” and “Request a Quote”.
17 calls to action
The homepage has 17 calls to action, for example “View Quote”, “Contact” and “Contact Form”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
12 cookies set on arrival
12Opening the homepage sets 12 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.
2 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 welding-alloys.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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on welding-alloys.com, including 22 speed issues, 1 SEO issue 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.