7.2 sec in total
1.9 sec
4.4 sec
814 ms
Click here to check amazing Starken Pixnet content for Taiwan. Otherwise, check out these important facts you probably never knew about starken.pixnet.net
個人心情發表、英文學習心得與資料收集
Visit starken.pixnet.netWe analyzed Starken.pixnet.net page load time and found that the first response time was 1.9 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
starken.pixnet.net performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value5.5 s
19/100
25%
Value15.7 s
0/100
10%
Value2,580 ms
4/100
30%
Value0.008
100/100
15%
Value26.8 s
0/100
10%
1901 ms
28 ms
31 ms
48 ms
40 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Starken.pixnet.net, 14% (17 requests) were made to Front.pixfs.net and 12% (14 requests) were made to S.pixfs.net. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Cmoney.tw.
Page size can be reduced by 290.1 kB (37%)
782.4 kB
492.2 kB
In fact, the total size of Starken.pixnet.net main page is 782.4 kB. 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 332.1 kB which makes up the majority of the site volume.
Potential reduce by 63.0 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.0 kB or 79% of the original size.
Potential reduce by 14.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. Starken Pixnet images are well optimized though.
Potential reduce by 166.8 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 166.8 kB or 54% of the original size.
Potential reduce by 45.7 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. Starken.pixnet.net needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 77% of the original size.
Number of requests can be reduced by 89 (77%)
116
27
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Starken Pixnet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
blog
1901 ms
lang-css.css
28 ms
iframe-popup.css
31 ms
plugins.min.css
48 ms
openid-comment.css
40 ms
style.min.css
69 ms
blogtopbar.min.css
78 ms
normal.css
88 ms
falcon-ad.css
25 ms
jquery.min.js
61 ms
jquery.onAppear.min.js
25 ms
json2.min.js
61 ms
angular.min.js
77 ms
spin.min.js
59 ms
angular-spinner.min.js
21 ms
checklogin.php
455 ms
checklogin.min.js
27 ms
en_US.js
21 ms
pix.min.js
21 ms
pix-addon.min.js
22 ms
all.min.js
17 ms
blog.min.js
17 ms
search_selection.min.js
23 ms
ad-full-page.min.js
22 ms
pixlogger.min.js
21 ms
checkloop.min.js
20 ms
swfobject.js
15 ms
mib_falcon.min.js
22 ms
4ecaa5e71086.js
653 ms
mixpanel.js
4 ms
blog-mixpanel.min.js
163 ms
c.js
99 ms
r.js
410 ms
blogtopbar.min.js
6 ms
tools.min.js
14 ms
analytics.js
63 ms
count.php
660 ms
checklogin.min.js
65 ms
49dacf25b7d67.png
1032 ms
20140905173150294.png
1916 ms
90x90.png
344 ms
blog.png
659 ms
pixnet-rss.gif
53 ms
pixnet-atom.gif
55 ms
reply-rss.gif
54 ms
expand.gif
54 ms
collapse.gif
54 ms
plus.gif
55 ms
atrk.js
117 ms
sticker
402 ms
49dacf266edde.png
979 ms
49dacf273c6a6.png
980 ms
49dacf294a496.png
980 ms
49d8d80e04fbf.png
980 ms
49d8d80e64345.png
981 ms
49d8d80ed9f42.png
984 ms
49d8d80f8b846.png
983 ms
49dacf25546bf.png
982 ms
49dacf261737a.png
983 ms
49dacf28052b9.png
983 ms
sprite.png
68 ms
latestcomment
328 ms
getdata.php
311 ms
atrk.gif
41 ms
test.png
219 ms
getcounter.php
482 ms
getcounter.php
511 ms
style.min.css
148 ms
jquery.min.js
15 ms
all.min.js
296 ms
google-analytics.min.js
294 ms
mixpanel.min.js
295 ms
checklogin
226 ms
av.gif
155 ms
mixpanel.2.js
33 ms
zoomcrop
270 ms
7hllogo.png
272 ms
7hltitle.png
274 ms
taghot.png
271 ms
clips.png
271 ms
zoomcrop
267 ms
zoomcrop
268 ms
bg.png
362 ms
imgbg.png
360 ms
overbg.png
361 ms
atrk.gif
29 ms
dc.js
41 ms
test.png
245 ms
26 ms
__utm.gif
12 ms
ada
791 ms
49dacf26c48d8.png
200 ms
mixpanel-2.2.min.js
179 ms
ga.js
41 ms
gtm.js
41 ms
gtm.js
42 ms
pa.gif
455 ms
pi.min.js
37 ms
production.js
174 ms
production.js
175 ms
production.js
174 ms
production.js
174 ms
plusone.js
160 ms
1020
460 ms
1029
471 ms
production.js
152 ms
pa.gif
464 ms
__utm.gif
102 ms
collect
154 ms
pi.gif
899 ms
collect
95 ms
collect
102 ms
49 ms
45 ms
cb=gapi.loaded_0
51 ms
i.gif
219 ms
f26b8df5684c4377b578a3dd1b68e1e3-9ffb3147b4b65e42.jpg
15 ms
ad-icon.png
13 ms
starken.pixnet.net accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
starken.pixnet.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
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
starken.pixnet.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Starken.pixnet.net 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 English language. Our system also found out that Starken.pixnet.net 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.
starken.pixnet.net
Open Graph data is detected on the main page of Starken Pixnet. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: