Website review, no card needed

aamataipei.com.tw logo

aamataipei.com.tw website review

Visit site (opens in a new tab)Reviewed 16 November 202641 issues · 82 checks

This review found 41 issues worth fixing on aamataipei.com.tw, 16 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.

  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
3.0 s1.5 sMay 30Nov 142.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.4 s
Jun 20, 20262.2 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.6 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.2 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20262.1 s
Oct 17, 20262.3 s
Oct 24, 20262.2 s
Oct 31, 20262.2 s
Nov 7, 20262.1 s
Nov 14, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
94 ms58 msMay 30Nov 1487 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202688 ms
Jun 6, 202690 ms
Jun 13, 202685 ms
Jun 20, 202677 ms
Jun 27, 202671 ms
Jul 4, 202677 ms
Jul 11, 202679 ms
Jul 18, 202686 ms
Jul 25, 202688 ms
Aug 1, 202683 ms
Aug 8, 202679 ms
Aug 15, 202678 ms
Aug 22, 202675 ms
Aug 29, 202677 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202670 ms
Sep 26, 202669 ms
Oct 3, 202664 ms
Oct 10, 202662 ms
Oct 17, 202690 ms
Oct 24, 202690 ms
Oct 31, 202690 ms
Nov 7, 202690 ms
Nov 14, 202687 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 aamataipei.com.tw (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aamataipei.com.tw at 0.5 s0.5 s
  2. aamataipei.com.tw at 1.0 s1.0 s
  3. aamataipei.com.tw at 1.5 s1.5 s
  4. aamataipei.com.tw at 2.0 s2.0 s
  5. aamataipei.com.tw at 2.5 s2.5 s
  6. aamataipei.com.tw at 3.0 s3.0 s
  7. aamataipei.com.tw at 3.5 s3.5 s
  8. aamataipei.com.tw at 4.1 s4.1 s

Speed

8 to fix53
  • Use efficient cache lifetimes

    23.1 s · 5.7 MB

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

  • Render-blocking requests

    23.6 s

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

  • Reduce unused CSS

    13.7 s · 2.7 MB

    About 2.7 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 13.7 s faster on a phone.

  • Reduce unused JavaScript

    3.6 s · 954 KiB

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

  • Improve image delivery

    2.1 s · 1.1 MB

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

  • Minify CSS

    1.4 s · 259 KiB

    259 KiB could be saved by minifying CSS.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 432 ms

    432 ms

    Google Tag Manager costs a phone 432 ms of main-thread work and 688 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.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 721 KiB and 433 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Font display

    150 ms

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

  • Document request latency

    142 KiB

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

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 397 ms

    397 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • First Contentful Paint: 20.9 s

    20.9 s

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

  • Largest Contentful Paint: 31.0 s

    31.0 s

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

  • Speed Index: 20.9 s

    20.9 s

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

  • Time to Interactive: 31.2 s

    31.2 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 12 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

4 checks passed
  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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.

  • Total Blocking Time: 164 ms

    164 ms

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

  • Cumulative Layout Shift: 0.04

    0.04

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

Images and page weight

3 to fix53
  • Page weight: 6.6 MB in 167 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 167 requests on a phone: stylesheets 2.8 MB (81), scripts 1.9 MB (59) and images 1.3 MB (15). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

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

  • 13 images below the first screen load straight away

    13 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.87 g

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

6 to fixGoogle 8490
  • 13 text elements with low contrast

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

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

    All page content should be contained by landmarks: 27 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.

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 28 automated accessibility rules passed

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

SEO

4 to fixGoogle 9277
  • 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: “AAMA 台北搖籃計畫 – AAMA台北搖籃計畫”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No robots.txt

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

  • 12 links crawlers can't follow

    12 links have no real href, so search engines can't follow them.

  • 56 internal links, 0 external

    The homepage links to 56 pages on aamataipei.com.tw and 0 external pages.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “AAMA 台北搖籃計畫是公益性創業服務計畫,以培育台灣下一代具指標性創業家為使命。 每年邀請 12 位成功創業家、高階經理人擔任導師,徴選 20 多位極具潛力的成長期創業家, 進行為期兩年的創業輔導,連結跨世代的經驗及資源,協助改變台灣社…”.

  • Canonical URL set

    The canonical URL is https://www.aamataipei.com.tw/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.aamataipei.com.tw/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

Other pages

3 to fix85
  • 14 pages without a meta description

    https://www.aamataipei.com.tw/about, https://www.aamataipei.com.tw/%E5%89%B5%E6%A5%AD%E8%80%85%E5%85%B1%E5%89%B5%E5%B9%B3%E5%8F%B0%E5%9F%BA%E9%87%91%E6%9C%83, https://www.aamataipei.com.tw/%e6%90%96%e7%b1%83%e5%b0%8e%e5%b8%ab, https://www.aamataipei.com.tw/%e6%90%96%e7%b1%83%e5%89%b5%e6%a5%ad%e5%ae%b6, https://www.aamataipei.com.tw/%e5%85%b1%e5%89%b5-2 and https://www.aamataipei.com.tw/blog/%e6%9c%80%e6%96%b0%e6%b6%88%e6%81%af and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 links to non-canonical URLs

    Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://www.aamataipei.com.tw/%e6%90%96%e7%b1%83%e5%b0%8e%e5%b8%ab, whose canonical is https://www.aamataipei.com.tw/%E6%90%96%E7%B1%83%E5%B0%8E%E5%B8%AB. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://www.aamataipei.com.tw/tccfe, https://www.aamataipei.com.tw/about, https://www.aamataipei.com.tw/blog/%e6%9c%80%e6%96%b0%e6%b6%88%e6%81%af, https://www.aamataipei.com.tw/blog/%e6%a0%a1%e5%8f%8b%e8%a8%aa%e8%ab%87, https://www.aamataipei.com.tw/blog/%e6%b4%bb%e5%8b%95%e7%b4%80%e9%8c%84 and https://www.aamataipei.com.tw/1 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://www.aamataipei.com.tw/tccfe, https://www.aamataipei.com.tw/about, https://www.aamataipei.com.tw/%E5%89%B5%E6%A5%AD%E8%80%85%E5%85%B1%E5%89%B5%E5%B9%B3%E5%8F%B0%E5%9F%BA%E9%87%91%E6%9C%83, https://www.aamataipei.com.tw/%e6%90%96%e7%b1%83%e5%b0%8e%e5%b8%ab, https://www.aamataipei.com.tw/%e5%85%b1%e5%89%b5-2 and https://www.aamataipei.com.tw/blog/%e6%9c%80%e6%96%b0%e6%b6%88%e6%81%af and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 4 pages slow to respond

    https://www.aamataipei.com.tw/%e6%90%96%e7%b1%83%e5%b0%8e%e5%b8%ab, https://www.aamataipei.com.tw/%e6%90%96%e7%b1%83%e5%89%b5%e6%a5%ad%e5%ae%b6, https://www.aamataipei.com.tw/aamaannualreport and https://www.aamataipei.com.tw/3 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • 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 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 30 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 63 words

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

  • 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
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 6 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
AWS

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 aamataipei.com.tw, including 17 speed issues, 4 SEO issues and 5 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