6.9 sec in total
1.5 sec
4.9 sec
480 ms
Welcome to izo.tw homepage info - get ready to check Izo best content for Taiwan right away, or after learning these important things about izo.tw
隨興,不隨便。 隨手紀錄,WordPress 與 WooCommerce 功能外掛客製化開發。 2023
Visit izo.twWe analyzed Izo.tw page load time and found that the first response time was 1.5 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
izo.tw performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value4.1 s
46/100
25%
Value4.9 s
65/100
10%
Value160 ms
93/100
30%
Value0.001
100/100
15%
Value7.1 s
52/100
10%
1521 ms
789 ms
504 ms
502 ms
820 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 46% of them (22 requests) were addressed to the original Izo.tw, 8% (4 requests) were made to Dsms0mj1bbhn4.cloudfront.net and 6% (3 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Izo.tw.
Page size can be reduced by 1.3 MB (75%)
1.7 MB
421.7 kB
In fact, the total size of Izo.tw main page is 1.7 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. 60% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 218.4 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 218.4 kB or 89% of the original size.
Potential reduce by 2.2 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. Izo images are well optimized though.
Potential reduce by 886.5 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 886.5 kB or 74% of the original size.
Potential reduce by 180.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. Izo.tw needs all CSS files to be minified and compressed as it can save up to 180.9 kB or 80% of the original size.
Number of requests can be reduced by 37 (82%)
45
8
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Izo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
izo.tw
1521 ms
wp-emoji-release.min.js
789 ms
style.css
504 ms
twentyfifteen.css
502 ms
crayon.min.css
820 ms
github.css
819 ms
consolas.css
966 ms
lightbox.min.css
1000 ms
css
69 ms
genericons.css
2411 ms
style.css
2766 ms
jetpack.css
2789 ms
jquery.min.js
57 ms
crayon.min.js
1242 ms
izo.tw
1651 ms
shareaholic.js
9 ms
ads.js
127 ms
script.js
1490 ms
photon.js
1544 ms
wp-lightbox-2.min.js
2209 ms
devicepx-jetpack.js
7 ms
skip-link-focus-fix.js
1972 ms
functions.js
2029 ms
jquery.sonar.min.js
2476 ms
lazy-load.js
2490 ms
count.js
2554 ms
e-201611.js
5 ms
analytics.js
53 ms
donate.png
989 ms
ads-iframe-display.php
87 ms
ef02c70f8c37bb8aed62f19ccd2ac6ac.json
80 ms
shrMain.min.js
49 ms
linkid.js
36 ms
1638105805608400_1_xacd.jpg
215 ms
Genericons.svg
510 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
12 ms
collect
65 ms
collect
202 ms
jquery.min.js
61 ms
count.js
137 ms
2728.png
157 ms
pageview.gif
78 ms
26f3.png
73 ms
count-data.js
127 ms
g.gif
54 ms
app.js
15 ms
angular.min.js
17 ms
shareaholic-icons.woff
10 ms
izo.tw accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
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.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
izo.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
izo.tw SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
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/).
Impact
Issue
Document uses legible font sizes
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Izo.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 Izo.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.
izo.tw
Open Graph data is detected on the main page of Izo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: