1.8 sec in total
292 ms
1.1 sec
460 ms
Click here to check amazing Totallyfuzzy content for United States. Otherwise, check out these important facts you probably never knew about totallyfuzzy.net
totallyfuzzy.net
Visit totallyfuzzy.netWe analyzed Totallyfuzzy.net page load time and found that the first response time was 292 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
totallyfuzzy.net performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value4.1 s
48/100
25%
Value3.5 s
88/100
10%
Value1,400 ms
16/100
30%
Value0
100/100
15%
Value19.2 s
2/100
10%
292 ms
20 ms
76 ms
6 ms
7 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Totallyfuzzy.net, 34% (24 requests) were made to I.ytimg.com and 23% (16 requests) were made to D1tewjuvj5u3n6.cloudfront.net. The less responsive or slowest element that took the longest time to load (387 ms) belongs to the original domain Totallyfuzzy.net.
Page size can be reduced by 57.6 kB (17%)
337.6 kB
280.0 kB
In fact, the total size of Totallyfuzzy.net main page is 337.6 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. 40% of websites need less resources to load. Images take 179.3 kB which makes up the majority of the site volume.
Potential reduce by 20.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 20.4 kB or 75% of the original size.
Potential reduce by 16.8 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. Totallyfuzzy images are well optimized though.
Potential reduce by 6.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 13.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. Totallyfuzzy.net needs all CSS files to be minified and compressed as it can save up to 13.7 kB or 79% of the original size.
Number of requests can be reduced by 21 (31%)
68
47
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Totallyfuzzy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
totallyfuzzy.net
292 ms
directory.style.v.2.2.css
20 ms
cookieconsent.latest.min.js
76 ms
show_ads.js
6 ms
adsbygoogle.js
7 ms
quant.js
9 ms
bg.jpg
58 ms
ca-pub-5106172995171796.js
60 ms
zrt_lookup.html
60 ms
show_ads_impl.js
62 ms
new_videos_iframe.php
387 ms
pixel;r=185061045;a=p-623g9EYxmoF5Q;fpan=1;fpa=P0-338473589-1456761287884;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456761287883;tzo=-180;ref=;url=http%3A%2F%2Ftotallyfuzzy.net%2F;ogl=
23 ms
ga.js
113 ms
bg2d.jpg
14 ms
optimized-fuzzy-banner-narrow2.jpg
19 ms
pixel.gif
19 ms
bg_menu_title.gif
19 ms
sprites.gif
19 ms
bg2.gif
130 ms
googleplus.24.png
132 ms
facebook.24.png
186 ms
twitter.24.png
132 ms
rss.24.png
186 ms
fuzzyplayerbutton-anim2.gif
28 ms
contentB.png
108 ms
body0000.png
126 ms
ads
206 ms
__utm.gif
20 ms
like.php
189 ms
osd.js
15 ms
ads
255 ms
ads
148 ms
ads.js
126 ms
vpc6VNjRPXV.js
223 ms
LVx-xkvaJ0b.png
246 ms
default.jpg
114 ms
bg_videos.gif
41 ms
default.jpg
155 ms
default.jpg
174 ms
default.jpg
195 ms
default.jpg
199 ms
default.jpg
198 ms
default.jpg
198 ms
default.jpg
196 ms
default.jpg
195 ms
default.jpg
198 ms
default.jpg
199 ms
default.jpg
201 ms
default.jpg
200 ms
default.jpg
200 ms
default.jpg
201 ms
default.jpg
201 ms
default.jpg
202 ms
default.jpg
202 ms
default.jpg
203 ms
default.jpg
202 ms
default.jpg
203 ms
default.jpg
204 ms
default.jpg
210 ms
default.jpg
210 ms
13863382943238019915
63 ms
abg.js
66 ms
m_js_controller.js
79 ms
googlelogo_color_112x36dp.png
114 ms
Color%20Alive%20Banners%202.12.16_CA_Mom_V2_altCopy_SeeHowItWorks_728x90.jpg
265 ms
ad
209 ms
ddcssl.htm
235 ms
s
39 ms
x_button_blue2.png
40 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
20 ms
pixel
28 ms
totallyfuzzy.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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
totallyfuzzy.net 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
Missing source maps for large first-party JavaScript
totallyfuzzy.net SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Totallyfuzzy.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Totallyfuzzy.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.
totallyfuzzy.net
Open Graph description is not detected on the main page of Totallyfuzzy. 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: