Website review, no card needed

axiomtek.com logo

axiomtek.com website review

Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 86 checks

This review found 41 issues worth fixing on axiomtek.com, 17 of them high impact, across 86 checks. The most urgent: google Tag Manager adds 9.6 s. 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
7.5 s2.9 sMay 16Oct 316.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.4 s
May 23, 20264.0 s
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.1 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.3 s
Jul 11, 20265.1 s
Jul 18, 20265.5 s
Jul 25, 20266.1 s
Aug 1, 20266.7 s
Aug 8, 20267.0 s
Aug 15, 20266.8 s
Aug 22, 20266.8 s
Aug 29, 20266.9 s
Sep 5, 20266.9 s
Sep 12, 20266.9 s
Sep 19, 20266.9 s
Sep 26, 20266.6 s
Oct 3, 20266.2 s
Oct 10, 20266.2 s
Oct 17, 20266.4 s
Oct 24, 20266.6 s
Oct 31, 20266.7 s
Real-visitor tap response (INP)75th percentile, phones
752 ms1 msMay 16Oct 31160 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026119 ms
May 23, 202688 ms
May 30, 2026102 ms
Jun 6, 2026109 ms
Jun 13, 2026102 ms
Jun 20, 2026106 ms
Jun 27, 2026110 ms
Jul 4, 2026120 ms
Jul 11, 2026124 ms
Jul 18, 2026123 ms
Jul 25, 2026111 ms
Aug 1, 2026102 ms
Aug 8, 202693 ms
Aug 15, 202699 ms
Aug 22, 2026104 ms
Aug 29, 2026102 ms
Sep 5, 2026114 ms
Sep 12, 2026125 ms
Sep 19, 2026230 ms
Sep 26, 2026665 ms
Oct 3, 2026441 ms
Oct 10, 2026238 ms
Oct 17, 2026166 ms
Oct 24, 2026155 ms
Oct 31, 2026160 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 axiomtek.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. axiomtek.com at 1.9 s1.9 s
  2. axiomtek.com at 3.7 s3.7 s
  3. axiomtek.com at 5.6 s5.6 s
  4. axiomtek.com at 7.4 s7.4 s
  5. axiomtek.com at 9.3 s9.3 s
  6. axiomtek.com at 11.1 s11.1 s
  7. axiomtek.com at 13.0 s13.0 s
  8. axiomtek.com at 14.9 s14.9 s

Speed

12 to fix30
  • Google Tag Manager adds 9.6 s

    9.6 s

    Google Tag Manager costs a phone 9.6 s of main-thread work and 886 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    2.7 s · 459 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Main-thread work: 13.1 s

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

  • Mobile performance score: 30

    30/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and JSDelivr CDN and others), adding 1.2 MB and 9.8 s of main-thread time.

  • 7 long tasks on the main thread

    7 long tasks block the main thread while loading, the longest for 5.5 s. During a long task the page ignores taps.

  • Improve image delivery

    5.2 MB

    18 images could be 5.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    450 ms · 164 KiB

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

  • Document request latency

    500 ms · 79 KiB

    The HTML itself could arrive about 500 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    517 ms

    Reduce initial server response time. Google estimates savings of 517 ms on a phone.

  • Server response: 617 ms

    617 ms

    Your server takes 617 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Font display

    50 ms

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

  • Minify CSS

    28 KiB

    28 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    17 KiB

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

  • 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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

Core Web Vitals

12 to fix50
  • 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 TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 15.6 s

    15.6 s

    Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Driving Intelligent Automation with IoT, AI, and Edge Compu…”.

  • Total Blocking Time: 11.2 s

    11.2 s

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

  • Speed Index: 14.5 s

    14.5 s

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

  • Time to Interactive: 21.7 s

    21.7 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

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

    +52%

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

  • Largest content (LCP) got 81% slower for real visitors

    +81%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • 9 images without width and height

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

2 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

1 to fix70
  • Page weight: 9.6 MB in 132 requests

    9.6 MB

    Your homepage downloads 9.6 MB in 132 requests on a phone: images 7.6 MB (51), scripts 1.0 MB (15) and fonts 638 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 2.7 g of CO₂ per visit

    2.71 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 9091
  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 36 elements on the page fail 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.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 55 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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

5 to fixGoogle 8575
  • No H1 headline

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

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Axiomtek- Industry Leader in Industrial Embedded Computer Solutions”.

  • Meta description is long (238 characters)

    Your meta description is 238 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 19 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 158 internal links, 13 external

    The homepage links to 158 pages on axiomtek.com and 13 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • 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.axiomtek.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

100
  • 1 page slow to respond

    https://www.axiomtek.com/products/boards-and-modules/industrial-and-embedded-motherboard/atx-motherboard took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    1 page of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 1 page 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 1 page that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 18 small tap targets

    18 of 44 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

2 to fix70
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 751 words of copy

    The homepage carries about 751 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us” and “Learn More”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 10 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Data Communication Business Group

Company

Employees
118
Founded
1990
Headquarters
Taipei

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on axiomtek.com, including 24 speed issues, 5 SEO issues and 2 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