tekweld.com website review

21 files are served with short cache lifetimes, so returning visitors download them again (22.2 MB).

19 images could be 21.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 28.1 s faster on a phone.

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

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

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

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

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

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

Google Maps costs a phone 136 ms of main-thread work and 328 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.

4 third-party services load with your homepage (Google Tag Manager, Google Maps and loginwithamazon.com and others), adding 542 KiB and 301 ms of main-thread time.

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

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

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

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

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

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

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

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

11 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 23.8 MB in 76 requests on a phone: images 22.2 MB (19), scripts 937 KiB (25) and fonts 307 KiB (2). Under 2 MB keeps phones on slow connections fast.

banner1790972989.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example banner1790972989.png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.5 MB.

5 images (2.5 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.

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

Required ARIA attributes must be provided: 1 element on the page fails 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 button has no accessible name, so screen readers announce just “button”.

10 elements hidden from screen readers can still receive keyboard focus.

5 tap targets are too small or too close together to hit reliably with a finger.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 21 characters: “Tekweld | tekweld.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

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 https://www.tekweld.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.

7 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Invalid href passed to next/router: https://www.promocorner.com/pageflip/Tekweld//?i=8278&p=1, repeated forward-slashes…”.

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 37 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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