6.6 sec in total
1.1 sec
4.6 sec
984 ms
Visit immian.com now to see the best up-to-date Immian content for Taiwan and also check out these interesting facts you probably never knew about immian.com
專職文字與攝影工作者,業餘的旅行家、不專業的咖啡品嚐師,提供國內外旅遊景點筆記、美食懶人包,立志踏遍全世界旅遊的芭樂點,再私藏一些沒人知道的祕密景點。
Visit immian.comWe analyzed Immian.com page load time and found that the first response time was 1.1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
immian.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value17.0 s
0/100
25%
Value10.4 s
8/100
10%
Value530 ms
55/100
30%
Value0.303
39/100
15%
Value17.0 s
4/100
10%
1058 ms
75 ms
597 ms
9 ms
30 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 33% of them (20 requests) were addressed to the original Immian.com, 18% (11 requests) were made to Img.immian.com and 8% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Img.immian.com.
Page size can be reduced by 293.6 kB (15%)
1.9 MB
1.6 MB
In fact, the total size of Immian.com main page is 1.9 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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 63.3 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 63.3 kB or 71% of the original size.
Potential reduce by 9.6 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. Immian images are well optimized though.
Potential reduce by 107.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 107.5 kB or 43% of the original size.
Potential reduce by 113.1 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. Immian.com needs all CSS files to be minified and compressed as it can save up to 113.1 kB or 82% of the original size.
Number of requests can be reduced by 30 (53%)
57
27
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Immian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
immian.com
1058 ms
analytics.js
75 ms
wp-emoji-release.min.js
597 ms
font-awesome.min.css
9 ms
css
30 ms
frontend.css
407 ms
flexslider.css
412 ms
style.css
419 ms
style.css
424 ms
jetpack.css
427 ms
jquery.js
1218 ms
jquery-migrate.min.js
617 ms
jquery.flexslider-min.js
837 ms
achang.custom.js
633 ms
adsbygoogle.js
7 ms
collect
27 ms
collect
90 ms
itm-tracker.js
323 ms
frontend.js
454 ms
devicepx-jetpack.js
53 ms
wp-embed.min.js
616 ms
e-201609.js
3 ms
itm-tracker.js
664 ms
2016-01-21-162928-32.jpg
1210 ms
2016-01-17-195706-19.jpg
1879 ms
2016-01-17-160312-11.png
2405 ms
2016-01-14-150119-79.jpg
1276 ms
2016-01-11-234722-24.jpg
1034 ms
2016-01-11-223711-46.jpg
1062 ms
aaDSCF2464.jpg
1758 ms
2016-01-07-232710-71.jpg
1558 ms
DSCF4046aaa.jpg
1421 ms
hqapp.jpg
1996 ms
b73f77fe2d0d39d8c8e1ff50c903ad7d.jpg
1871 ms
headerimage.png
247 ms
date.png
246 ms
sidebar-icon.gif
246 ms
search.gif
245 ms
li.png
244 ms
ca-pub-7585725358552791.js
173 ms
zrt_lookup.html
162 ms
show_ads_impl.js
162 ms
blogembed.php
217 ms
footer-logo.png
221 ms
fbox.png
364 ms
sdk.js
260 ms
g.gif
13 ms
ads
264 ms
osd.js
11 ms
147 ms
xd_arbiter.php
161 ms
xd_arbiter.php
259 ms
m_js_controller.js
29 ms
abg.js
52 ms
favicon
72 ms
googlelogo_color_112x36dp.png
72 ms
nessie_icon_tiamat_white.png
35 ms
s
18 ms
x_button_blue2.png
9 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
11 ms
immian.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
immian.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
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
immian.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Immian.com 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 Immian.com 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.
immian.com
Open Graph data is detected on the main page of Immian. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: