tku.edu.tw website review

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

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

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

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.

888 KiB could be saved by minifying JavaScript.

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

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

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

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

6 third-party services load with your homepage (Cloudflare CDN, Google Tag Manager and JSDelivr CDN and others), adding 617 KiB and 363 ms of main-thread time.

About 62 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.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

Your largest element takes 40.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “01刊頭_76校慶”.

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

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

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

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

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

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

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

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

Your homepage downloads 38.2 MB in 228 requests on a phone: images 35.5 MB (119), scripts 2.4 MB (70) and fonts 157 KiB (2). Under 2 MB keeps phones on slow connections fast.

20261029_76校慶.jpg weighs 667 KiB. On a phone connection a single image that size takes seconds.

1 image (667 KiB) is 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.

1 image is downloaded at several times the size a phone draws it, for example 20261029_76校慶.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 419 KiB.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

Headings skip levels (h4 → h6), which makes the page harder to scan with a screen reader.

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

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

Your title is only 6 characters: “淡江大學網站”. 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 Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

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

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

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

The homepage links to 31 pages on tku.edu.tw and 173 external pages.

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.tku.edu.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.

/ and https://www.tku.edu.tw/tku all use the title “淡江大學網站”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tku.edu.tw/tku has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tku.edu.tw/tku has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tku.edu.tw/tku took over 3 s to send its HTML from our server.

We fetched 1 page linked from your homepage and read each the way a search engine does.

2 images failed to load on a phone, for example https://www.tku.edu.tw/.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

Large scripts ship without source maps.

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

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

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

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

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

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 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 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.