Website review, no card needed

twusa.com logo

twusa.com website review

Visit site (opens in a new tab)Reviewed 24 October 202642 issues · 66 checks

This review found 42 issues worth fixing on twusa.com, 17 of them high impact, across 66 checks. The most urgent: use efficient cache lifetimes. 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
4.3 s3.5 sMay 2Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.1 s
May 16, 20264.2 s
May 23, 20264.2 s
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.1 s
Jun 20, 20263.9 s
Jun 27, 20263.8 s
Jul 4, 20263.8 s
Jul 11, 20263.8 s
Jul 18, 20263.7 s
Jul 25, 20263.8 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.9 s
Aug 22, 20263.8 s
Aug 29, 20264.0 s
Sep 5, 20263.9 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.2 s
Oct 10, 20264.0 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
135 ms94 msMay 2Oct 17107 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026112 ms
May 9, 2026112 ms
May 16, 2026111 ms
May 23, 2026113 ms
May 30, 2026119 ms
Jun 6, 2026113 ms
Jun 13, 2026117 ms
Jun 20, 2026119 ms
Jun 27, 2026118 ms
Jul 4, 2026130 ms
Jul 11, 2026130 ms
Jul 18, 2026130 ms
Jul 25, 2026129 ms
Aug 1, 2026125 ms
Aug 8, 2026113 ms
Aug 15, 2026105 ms
Aug 22, 2026104 ms
Aug 29, 202699 ms
Sep 5, 2026104 ms
Sep 12, 2026106 ms
Sep 19, 2026116 ms
Sep 26, 2026119 ms
Oct 3, 2026115 ms
Oct 10, 2026110 ms
Oct 17, 2026107 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 twusa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix46
  • Use efficient cache lifetimes

    7.8 s · 9.4 MB

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

  • Improve image delivery

    7.5 s · 9.2 MB

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

  • Mobile performance score: 46

    46/100

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

  • Reduce unused JavaScript

    750 ms · 148 KiB

    About 148 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 40 KiB

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

  • Render-blocking requests

    150 ms

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

  • 2 long tasks on the main thread

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

  • Font display

    100 ms

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

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Amazon Web Services), adding 9 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 443 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.77

    0.77

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

  • Largest Contentful Paint: 13.0 s

    13.0 s

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

  • Cumulative Layout Shift: 0.794

    0.794

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

  • Time to Interactive: 13.0 s

    13.0 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 91 ms

    91 ms

    Scripts block the page for only 91 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix25
  • 9 images over 500 KB

    9 images weigh 9.3 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 9.9 MB in 62 requests

    9.9 MB

    Your homepage downloads 9.9 MB in 62 requests on a phone: images 9.4 MB (22), scripts 340 KiB (26) and fonts 58 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 9 images far larger than shown

    7.7 MB

    9 images are downloaded at several times the size a phone draws them, for example Acquisition Web Banner-Optimized.png at 2,800 px wide, shown at 390 px. Resized copies would save about 7.7 MB.

  • 9 images in older formats

    9 images (9.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.

  • About 2.8 g of CO₂ per visit

    2.80 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fixGoogle 9291
  • 2 tap targets too small

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

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

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

  • Main landmark should not be contained in another landmark (1 element)

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

  • Page should contain a level-one heading (1 element)

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

  • 4 links without text

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

9 to fixGoogle 8352
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (24 characters)

    Your title is only 24 characters: “Welcome to TechniweldUSA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at twusa.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 156 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Best practices

2 to fixGoogle 9687
  • 31 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “User is not authenticated UserUnAuthenticatedException: User needs to be authenticated to call this API.”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No calls to action

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

  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 156 words

    The homepage has only about 156 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register now” and “CONTACT”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • No consent tool detected

    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.

  • 3 other companies contacted

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

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 twusa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
Netlify

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 twusa.com, including 13 speed issues, 9 SEO issues and 4 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