udn.com website review

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

Google/Doubleclick Ads costs a phone 1.9 s of main-thread work and 2.7 MB 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.

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

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

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

8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Facebook and others), adding 17.6 MB and 2.9 s of main-thread time.

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

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

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

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

Facebook costs a phone 212 ms of main-thread work and 380 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.

Taboola costs a phone 206 ms of main-thread work and 375 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.

viverse.com costs a phone 145 ms of main-thread work and 952 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.

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

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

11 KiB could be saved by minifying CSS.

Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

16 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 18.2 MB in 527 requests on a phone: fonts 9.8 MB (160), scripts 4.2 MB (95) and images 1.5 MB (60). Under 2 MB keeps phones on slow connections fast.

photo.php is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image (213 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.

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

3 images have no alt text, which hurts accessibility and image search.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner 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 on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

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

Your title is only 13 characters: “聯合新聞網：觸動未來新識力”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 324 pages on udn.com and 204 external pages.

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

robots.txt blocks GPTBot and ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://udn.com/news/index declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://udn.com/news/index all use the title “聯合新聞網：觸動未來新識力”. Search engines can't tell which page to show for a search, so each competes with the others.

https://udn.com/news/index, https://udn.com/news/breaknews/1, https://udn.com/news/cate/2/7227, https://udn.com/news/cate/2/7225, https://udn.com/news/cate/2/6639 and https://udn.com/news/cate/2/6641 and 6 others use the same meta description. A description written for each page earns more clicks.

https://udn.com/news/index, https://udn.com/news/breaknews/1, https://udn.com/news/cate/2/6638, https://udn.com/vote2026/index, https://udn.com/news/cate/2/7227 and https://udn.com/news/cate/2/7225 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://udn.com/news/breaknews/1, https://udn.com/vote2026/index, https://udn.com/news/cate/2/6643 and https://udn.com/news/cate/2/6640 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.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'split')”.

Chrome logged issues while loading the page (“Cookie”).

Requests the notification permission on page load.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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 Comscore, Criteo, Google Ads, Google Analytics and Google Tag Manager and 3 mores (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.

Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).

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