Website review, no card needed

aswo.com logo

aswo.com website review

Visit site (opens in a new tab)Reviewed 28 October 202636 issues · 80 checks

This review found 36 issues worth fixing on aswo.com, 11 of them high impact, across 80 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
990 ms844 msMay 9Oct 24934 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026861 ms
May 16, 2026861 ms
May 23, 2026900 ms
May 30, 2026924 ms
Jun 6, 2026961 ms
Jun 13, 2026973 ms
Jun 20, 2026937 ms
Jun 27, 2026907 ms
Jul 4, 2026888 ms
Jul 11, 2026875 ms
Jul 18, 2026870 ms
Jul 25, 2026875 ms
Aug 1, 2026889 ms
Aug 8, 2026910 ms
Aug 15, 2026927 ms
Aug 22, 2026921 ms
Aug 29, 2026930 ms
Sep 5, 2026919 ms
Sep 12, 2026910 ms
Sep 19, 2026928 ms
Sep 26, 2026914 ms
Oct 3, 2026926 ms
Oct 10, 2026926 ms
Oct 17, 2026933 ms
Oct 24, 2026934 ms
Real-visitor tap response (INP)75th percentile, phones
105 ms92 msMay 9Oct 2495 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202693 ms
May 16, 202694 ms
May 23, 202695 ms
May 30, 202696 ms
Jun 6, 2026102 ms
Jun 13, 2026100 ms
Jun 20, 2026101 ms
Jun 27, 2026101 ms
Jul 4, 2026101 ms
Jul 11, 2026102 ms
Jul 18, 2026102 ms
Jul 25, 2026103 ms
Aug 1, 2026102 ms
Aug 8, 2026101 ms
Aug 15, 202698 ms
Aug 22, 202696 ms
Aug 29, 202697 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 202695 ms
Oct 3, 202694 ms
Oct 10, 202696 ms
Oct 17, 202693 ms
Oct 24, 202695 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 aswo.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aswo.com at 1.1 s1.1 s
  2. aswo.com at 2.1 s2.1 s
  3. aswo.com at 3.2 s3.2 s
  4. aswo.com at 4.3 s4.3 s
  5. aswo.com at 5.4 s5.4 s
  6. aswo.com at 6.4 s6.4 s
  7. aswo.com at 7.5 s7.5 s
  8. aswo.com at 8.6 s8.6 s

Speed

7 to fix86
  • Use efficient cache lifetimes

    2.2 s · 5.2 MB

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

  • Font display

    3.0 s

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

  • Mobile performance score: 86

    86/100

    Your mobile performance score is 86 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

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

  • Improve image delivery

    150 ms · 507 KiB

    10 images could be 507 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 57 KiB

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

  • Main-thread work: 2.4 s

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

  • 8 long tasks on the main thread

    8 long tasks block the main thread while loading, the longest for 214 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.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 3.8 s

    3.8 s

    Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website only uses session cookies. For further details…”. Most of its time is element render delay (2.3 s).

  • Speed Index: 3.9 s

    3.9 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 11 images without width and height

    11 images 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-24, real Chrome visitors' tap response (inp) went from 93 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

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

9 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: 1.0 s

    1.0 s

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

  • Real-user INP: 91 ms

    91 ms

    Real visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (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: 501 ms

    501 ms

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

  • Time to Interactive: 3.8 s

    3.8 s

    The page is fully interactive after 3.8 s.

  • Cumulative Layout Shift: 0.005

    0.005

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

  • Total Blocking Time: 3 ms

    3 ms

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

Images and page weight

4 to fix38
  • Page weight: 5.2 MB in 155 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 155 requests on a phone: images 4.7 MB (132), fonts 324 KiB (8) and stylesheets 65 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

  • 14 images in older formats

    14 images (3.7 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.

  • 7 images below the first screen load straight away

    7 images further down the page (452 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.1 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

9 to fixGoogle 7386
  • Certain ARIA roles must be contained by particular parents (3 elements)

    Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.

  • Unlabelled dropdowns

    2 dropdowns have no label.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 4 text elements with low contrast

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

  • 3 tap targets too small

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

  • Malformed lists

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

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

  • 4 form fields without a label

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 131 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 8374
  • No meta description

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

  • No structured data

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

  • 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.aswo.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 83 internal links, 1 external

    The homepage links to 83 pages on aswo.com and 1 external page.

3 checks passed
  • One H1 headline

    Your main headline reads: “Back to home page”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “ASWO, Excellence in After-Sales Services”.

  • Canonical URL set

    The canonical URL is https://www.aswo.com/.

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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.aswo.com/data-privacy, https://www.aswo.com/need-help, https://www.aswo.com/solutions, https://www.aswo.com/solutions/spare-parts-logistic, https://www.aswo.com/solutions/e-commerce-solutions and https://www.aswo.com/solutions/warranty-services and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 29 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.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Thin social proof

    Social proof on the homepage: “Over 3.000 brands”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

  • About 397 words of copy

    The homepage carries about 397 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Retailers Learn more” and “Manufacturers Learn more”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop”, “Order Spare Parts” and “Contact us”.

  • 1 short form

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

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

1 checks passed
  • 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 aswo.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
TYPO3 CMS
Framework
jQuery
Hosting
Internet service provider operations

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on aswo.com, including 11 speed issues, 6 SEO issues and 3 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