Access 365net.tw. 台灣旅遊通

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.157

74/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

365net.tw

557 ms

365net.tw

1716 ms

astyle.css

887 ms

astyle1.css

920 ms

sub_01.gif

232 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 83% of them (84 requests) were addressed to the original 365net.tw, 3% (3 requests) were made to Pagead2.googlesyndication.com and 3% (3 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain 365net.tw.

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of 365net.tw main page is 1.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 783.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 55.9 kB

Original 67.5 kB
After minification 66.5 kB
After compression 11.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 297 B

Original 783.7 kB
After minification 783.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. 365 Net images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 72.4 kB

Original 370.3 kB
After minification 369.4 kB
After compression 298.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 72.4 kB or 20% of the original size.

CSS Optimization

-83%

Potential reduce by 9.1 kB

Original 11.0 kB
After minification 8.4 kB
After compression 1.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. 365net.tw needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 83% of the original size.

Requests Now

After Optimization

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 365 Net. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

ZH
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 365net.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that 365net.tw main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

365net.tw

Open Graph description is not detected on the main page of 365 Net. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

台灣旅遊通

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

365net.tw

365net.tw

astyle.css

astyle1.css

sub_01.gif

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

365net.tw

365net.tw

astyle.css

astyle1.css

sub_01.gif

sub_logo.gif

sb.gif

sub_03.gif

sub_01a.gif

case_a01.gif

case_a03.gif

300_100_kite.jpg

show_ads.js

case_b01.gif

abs_in01_yilan_4.jpg

for_02.gif

hot.gif

abs_in01_hualian_yue-sy.jpg

abs_in01_taitung_yiti.jpg

abs_in01_taichung_inlove.jpg

more.gif

case_b03.gif

abs_in04.jpg

abs_in01_miaoli_1.jpg

abs_in02.jpg

abs_in03.jpg

sub_01.gif

sub_logo.gif

sub_03.gif

sb.gif

sub_03a.gif

sub_02.jpg

like.php

abs_640.htm

in_ad_2010_a.asp

bk_bg.jpg

up_468_1.gif

taitou_1.png

taitou_2.png

sub_05.jpg

4.htm

travel.asp

ind_450_taitung.jpg