14.8 sec in total
146 ms
14.1 sec
495 ms
Visit fairyfish.net now to see the best up-to-date Fairyfish content and also check out these interesting facts you probably never knew about fairyfish.net
Visit fairyfish.netWe analyzed Fairyfish.net page load time and found that the first response time was 146 ms and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fairyfish.net performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value1.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.2 s
100/100
10%
146 ms
454 ms
3811 ms
1219 ms
5194 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fairyfish.net, 30% (20 requests) were made to 77flz7.com1.z0.glb.clouddn.com and 20% (13 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (8.3 sec) relates to the external source Wpjam.qiniudn.com.
Page size can be reduced by 223.0 kB (29%)
758.4 kB
535.4 kB
In fact, the total size of Fairyfish.net main page is 758.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. 45% of websites need less resources to load. Images take 395.9 kB which makes up the majority of the site volume.
Potential reduce by 31.1 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 31.1 kB or 74% of the original size.
Potential reduce by 53.9 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. Obviously, Fairyfish needs image optimization as it can save up to 53.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 123.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 123.8 kB or 41% of the original size.
Potential reduce by 14.2 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. Fairyfish.net needs all CSS files to be minified and compressed as it can save up to 14.2 kB or 69% of the original size.
Number of requests can be reduced by 38 (62%)
61
23
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fairyfish. 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 5 to 1 for CSS and as a result speed up the page load time.
fairyfish.net
146 ms
blog.wpjam.com
454 ms
normalize.min.css
3811 ms
wpjam.css
1219 ms
jquery.min.js
5194 ms
adsbygoogle.js
5 ms
wpjam.js
2459 ms
share.js
689 ms
push.js
1450 ms
views.js
1042 ms
analytics.js
37 ms
hm.js
1265 ms
container_bg.gif
1035 ms
qiniu.png
2861 ms
header_bg.jpg
7257 ms
logo.png
1287 ms
wordpress-tips.png
1492 ms
wp-blue-640x960.png
2013 ms
fenxingqiu-admin-list.png
2524 ms
php-logo.jpg
2289 ms
qiniu-logo.png
1736 ms
webhostingpad.png
4486 ms
weui.png
2180 ms
wpjam-basic.png
3152 ms
wp-dkblue-blue-640x960.png
2608 ms
fenxingqiu-admin-list.png
4051 ms
wp-orange-640x960.png
3866 ms
qiniu-logo.png
3027 ms
webhostingpad.jpg
8268 ms
weixin-qrcode.jpg
5436 ms
ca-pub-2251382466733231.js
191 ms
zrt_lookup.html
190 ms
show_ads_impl.js
114 ms
subcontent_bg.gif
3409 ms
post.gif
3601 ms
footer_bg.gif
3848 ms
share_api.js
329 ms
share_view.js
536 ms
slide_api.js
550 ms
slide_view.js
548 ms
collect
79 ms
collect
124 ms
ads
242 ms
osd.js
10 ms
css
65 ms
m_js_controller.js
39 ms
abg.js
37 ms
tangram.js
1163 ms
api_base.js
423 ms
favicon
60 ms
nessie_icon_thin_arrow_big_white.png
35 ms
s
18 ms
googlelogo_color_112x36dp.png
48 ms
x_button_blue2.png
13 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
3 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
47 ms
view_base.js
241 ms
hm.gif
426 ms
s.js
3680 ms
share_style0_24.css
232 ms
slide_share.css
224 ms
activeview
12 ms
r0.gif
237 ms
icons_0_16.png
446 ms
logger.js
230 ms
ui
35 ms
fairyfish.net 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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
fairyfish.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
fairyfish.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fairyfish.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Fairyfish.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.
fairyfish.net
Open Graph description is not detected on the main page of Fairyfish. 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: