8 sec in total
757 ms
6.5 sec
756 ms
Click here to check amazing Story Yipee content for Taiwan. Otherwise, check out these important facts you probably never knew about story.yipee.cc
生命中有許多感人的片段文章,形成各式各樣不同的記憶書籤
Visit story.yipee.ccWe analyzed Story.yipee.cc page load time and found that the first response time was 757 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
story.yipee.cc performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value13.7 s
0/100
25%
Value19.0 s
0/100
10%
Value1,540 ms
13/100
30%
Value0.022
100/100
15%
Value21.0 s
1/100
10%
757 ms
14 ms
498 ms
517 ms
507 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 26% of them (23 requests) were addressed to the original Story.yipee.cc, 34% (30 requests) were made to Image.yipee.cc and 25% (22 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Story.yipee.cc.
Page size can be reduced by 248.3 kB (20%)
1.3 MB
1.0 MB
In fact, the total size of Story.yipee.cc main page is 1.3 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. Images take 967.8 kB which makes up the majority of the site volume.
Potential reduce by 48.7 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 48.7 kB or 77% of the original size.
Potential reduce by 40.7 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. Story Yipee images are well optimized though.
Potential reduce by 59.9 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 59.9 kB or 58% of the original size.
Potential reduce by 99.0 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. Story.yipee.cc needs all CSS files to be minified and compressed as it can save up to 99.0 kB or 80% of the original size.
Number of requests can be reduced by 37 (43%)
86
49
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Story Yipee. 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 13 to 1 for CSS and as a result speed up the page load time.
story.yipee.cc
757 ms
cloudflare.min.js
14 ms
pagenavi-css.css
498 ms
superfish.css
517 ms
style.css
507 ms
2c-r-fixed.css
486 ms
base.css
3852 ms
default.css
988 ms
story2yipee.css
1026 ms
jetpack.css
792 ms
colorbox.min.css
1273 ms
rocket.js
979 ms
ysm_hotword_yipee.css
7 ms
bag2
175 ms
ga.js
89 ms
story-banner-ver13.png
301 ms
content-bg.jpg
556 ms
topnav.jpg
487 ms
rss.png
554 ms
facebook.png
507 ms
foreground.png
546 ms
prev.png
492 ms
next.png
994 ms
feed-title-white.jpg
1647 ms
comments.gif
1012 ms
Banner-%E4%B9%9D%E6%98%9F%E5%A4%A9%E5%9F%8E%E8%A8%A3-468x60.gif
75 ms
1337498372xGTC-610x300.jpg
305 ms
260333-13051204393040-600x300.jpg
329 ms
s1713.jpg
303 ms
s189.jpg
281 ms
1343003165_h3RSDp-550x300.jpg
327 ms
s622.jpg
476 ms
s810.jpg
393 ms
Zodiac-sign-Sagittarius-josh-shirohige1939-32750674-1024-768-195x110.jpg
519 ms
13-7-5-%E4%B8%8B%E5%8D%888-24-09-195x110.jpg
471 ms
Zodiac-sign-Gemini-josh-shirohige1939-32750770-1024-768-195x110.jpg
503 ms
s1142.jpg
534 ms
s2318.jpg
498 ms
s2288.jpg
812 ms
s3388.jpg
813 ms
s320.jpg
740 ms
s8291.jpg
813 ms
s2272.jpg
645 ms
s3105.jpg
542 ms
s967.jpg
721 ms
Snapshoot-2015-01-17-11.32.13-195x110.jpg
856 ms
s774.jpg
926 ms
s819.jpg
942 ms
s780.jpg
845 ms
ae670b91-cd3e-4a5d-b00d-75f31bda792d-195x110.jpg
844 ms
APP-DOWNLOAD-FREE-ICON.png
811 ms
LINE-yipee-280x85-v4.jpg
811 ms
webgame201502-280x85-v1.jpg
811 ms
415cf96e1ee93c34f64514c766135031.png
855 ms
__utm.gif
16 ms
postbar-black.gif
1995 ms
collect
67 ms
r_arrow.png
1995 ms
likebox.php
130 ms
jTuqQ-OPDr6.css
175 ms
n370yiaI2G6.css
213 ms
uzCGVqplqq-.css
253 ms
_rx8naC75Dy.js
329 ms
x5F9OMjKyLw.js
369 ms
ICDbTSzjQEg.js
413 ms
TTCre3391I0.js
292 ms
rFmE1g6Dkoz.js
419 ms
7cm7D75Y0Sf.js
344 ms
C-h3nYPqETO.js
386 ms
oRoBXlHCpEy.js
384 ms
336JejShbZp.js
386 ms
sj-JwAJi4AH.js
404 ms
DKRU1bYTkTw.js
454 ms
ZNPAadQNc33.js
457 ms
W0OV23mIOyO.js
458 ms
36TdwhIHusi.js
462 ms
295436_338720412876998_1814899619_n.jpg
261 ms
12243059_932483660167334_4576820727446443917_n.jpg
357 ms
10354686_10150004552801856_220367501106153455_n.jpg
383 ms
936616_941939192509902_7268453746182557813_n.jpg
421 ms
12670317_10207719277273509_2807168372694773630_n.jpg
385 ms
12631475_1677327225889630_1534642088818153108_n.jpg
415 ms
12743950_207227536297559_2829671571190401649_n.jpg
487 ms
12733384_1214908901857021_9146509456071955310_n.jpg
442 ms
wL6VQj7Ab77.png
77 ms
s7jcwEQH7Sx.png
77 ms
pUFVdPjIRct.png
41 ms
I6-MnjEovm5.js
42 ms
vlXaquuXMrr.js
45 ms
story.yipee.cc accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
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.
story.yipee.cc 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
story.yipee.cc 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
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 Story.yipee.cc 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 Story.yipee.cc 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.
story.yipee.cc
Open Graph data is detected on the main page of Story Yipee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: