fetnet.net website review

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

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

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

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

Google Tag Manager costs a phone 3.7 s of main-thread work and 3.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.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and 91app.com and others), adding 7.1 MB and 4.7 s of main-thread time.

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

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

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

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

friday.tw costs a phone 127 ms of main-thread work and 2.7 MB 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.

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

91app.com costs a phone 267 ms of main-thread work and 9 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.

18 KiB could be saved by minifying CSS.

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 9.8 s on a phone. Good is under 1.8 s.

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

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

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

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

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

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

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

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

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

The layout shifts by 0.245 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 16.6 MB in 372 requests on a phone: scripts 6.0 MB (91), media 4.2 MB (5) and images 2.3 MB (118). Under 2 MB keeps phones on slow connections fast.

01-tab1-4-385x746.jpg 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).

16 images (775 KiB) 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.

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

Images must have alternative text: 11 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.

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

54 elements hidden from screen readers can still receive keyboard focus.

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 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.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is only 22 characters: “新網路世代 首選新遠傳-遠傳電信FETnet”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 63 characters: “遠傳電信以用戶提供各類上網費率、續約與資費、線上申辦、帳單瀏覽與繳費、國際電話/漫遊、客戶服務、各類電信/會員優惠活動等服務。”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 358 pages on fetnet.net and 233 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 /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.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example /estore/exclusive/499.html, whose canonical is /content/cbu/estore/exclusive/499.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/estore/rateplan and /estore/rateplan/theme-number have no <h1> headline, so visitors and search engines get no clear main topic.

/estore/rateplan and /estore/rateplan/theme-number 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.

/estore/exclusive/499.html, /estore/exclusive/5g.html, /estore/exclusive/3c.html, /content/cbu/tw/promotion/iPhone/iPhone.html, /content/cbu/tw/promotion/Device/SepHSAlone/promotion/Samsung.html and /content/cbu/tw/postpaid/rateplan.html and 2 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://cm.g.doubleclick.net/pixel?google_nid=ad2iction_tw&google_cm&ad2id=6ae32a6c89ca99.369796861d963c70d5aacd88ab8f5b1a5629fdec.

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fetnet.net has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

fetnet.net's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 211 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

fetnet.net has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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 25 cookies (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 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.