10.9 sec in total
2.6 sec
7.6 sec
748 ms
Welcome to fuzzyfreak.com homepage info - get ready to check Fuzzyfreak best content for United States right away, or after learning these important things about fuzzyfreak.com
Celebrity News and Gossip
Visit fuzzyfreak.comWe analyzed Fuzzyfreak.com page load time and found that the first response time was 2.6 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fuzzyfreak.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.3 s
42/100
25%
Value4.1 s
79/100
10%
Value1,050 ms
25/100
30%
Value0.078
95/100
15%
Value6.9 s
54/100
10%
2565 ms
115 ms
172 ms
173 ms
188 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 28% of them (39 requests) were addressed to the original Fuzzyfreak.com, 8% (11 requests) were made to Sumome-140a.kxcdn.com and 8% (11 requests) were made to Sumome.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Fuzzyfreak.com.
Page size can be reduced by 1.5 MB (57%)
2.7 MB
1.2 MB
In fact, the total size of Fuzzyfreak.com main page is 2.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 121.5 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 121.5 kB or 83% of the original size.
Potential reduce by 142.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. Obviously, Fuzzyfreak needs image optimization as it can save up to 142.7 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 274.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 274.7 kB or 58% of the original size.
Potential reduce by 971.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. Fuzzyfreak.com needs all CSS files to be minified and compressed as it can save up to 971.0 kB or 92% of the original size.
Number of requests can be reduced by 62 (48%)
130
68
The browser has sent 130 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fuzzyfreak. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.fuzzyfreak.com
2565 ms
wp-emoji-release.min.js
115 ms
styles.css
172 ms
nivo-lightbox.css
173 ms
default.css
188 ms
pagenavi-css.css
174 ms
wbounce.css
186 ms
style.css
266 ms
css
31 ms
tablepress-combined.min.css
238 ms
jetpack.css
291 ms
default.css
289 ms
jquery.js
393 ms
jquery-migrate.min.js
306 ms
nivo-lightbox.min.js
362 ms
front.js
367 ms
wbounce-ck.js
376 ms
public.js
386 ms
load.sumome.com
306 ms
infolinks_main.js
72 ms
adsbygoogle.js
12 ms
jquery.form.min.js
430 ms
scripts.js
462 ms
tie-scripts.js
530 ms
wp-embed.min.js
461 ms
ice.js
120 ms
body-bg1.png
227 ms
logo1-300x73.png
231 ms
2013_bmw_335i_m_sport_4-1024x626-300x160.jpg
231 ms
leech-300x160.jpg
412 ms
jennifer_lopez-300x160.jpg
428 ms
linsay-300x160.jpg
118 ms
52-300x160.jpg
427 ms
girl_jumping_small-290x160.png
573 ms
26-300x160.jpg
426 ms
metalikes41-300x160.jpg
425 ms
disaster1-300x160.jpg
517 ms
WTF-Japonais-jeu-televise-japon-300x160.jpg
570 ms
forez-300x160.png
774 ms
bad_skin-300x160.png
829 ms
snoring-300x160.jpg
570 ms
analytics.js
18 ms
top-shadow.png
547 ms
tiefontello.svg
642 ms
tiefontello.woff
643 ms
ca-pub-8180676518095595.js
437 ms
zrt_lookup.html
433 ms
show_ads_impl.js
340 ms
collect
115 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
308 ms
bH7276GfdCjMjApa_dkG6T8E0i7KZn-EPnyo3HZu7kw.woff
403 ms
14601455748161
361 ms
collect
430 ms
widget.aspx
334 ms
widget.aspx
332 ms
widget.aspx
332 ms
all.js
319 ms
355 ms
ads
302 ms
osd.js
55 ms
ads
870 ms
GetWidget.aspx
197 ms
GetWidget.aspx
202 ms
doq.htm
193 ms
GetWidget.aspx
181 ms
751 ms
xd_arbiter.php
113 ms
xd_arbiter.php
733 ms
7331527271865348658
785 ms
abg.js
785 ms
m_js_controller.js
817 ms
service.js
529 ms
service.js
585 ms
42dbf461f66f207fa1dee5276c937ff0.jpg
48 ms
fatdiminisherbeachwoman.jpg
585 ms
c_ad_logo.png
45 ms
testosteronecoupleundressingeachother150x150.jpg
617 ms
testosteronehlwwhur.jpg
520 ms
tophattermichaelkorsbag2.jpg
717 ms
8582bde79a0afca171aa83c7ce32a913.jpg
41 ms
6fbb14137a7249983637a903ada980e7.jpg
40 ms
6556ee6c93bc5edd3138e1e1ccc58a2f.jpg
518 ms
aeb8cca356fa8f820773bee4e65841aa.jpg
517 ms
f52e2ddc7f364ea57fe13b186fbbebca.jpg
50 ms
pixel.gif
629 ms
googlelogo_color_112x36dp.png
757 ms
quantcast.js
663 ms
getads.htm
646 ms
loader.gif
332 ms
loader-bg.png
332 ms
load
307 ms
xe1wedge.png
205 ms
testosteronekitchencouple.jpg
206 ms
pixel.gif
162 ms
pixel.gif
161 ms
sumome-image-sharer.css
157 ms
sumome-share-client.css
88 ms
load
324 ms
css
55 ms
quant.js
107 ms
x_button_blue2.png
88 ms
favicon
87 ms
s
49 ms
mobile_unified_button_icon_white.png
54 ms
redir.html
104 ms
pixel;r=645123542;a=p-aRAyv335QWAKb;fpan=1;fpa=P0-104443861-1460145576300;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1460145576300;tzo=-180;ref=;url=http%3A%2F%2Fwww.fuzzyfreak.com%2F;ogl=site_name.Fuzzy%20Freak%2Ctype.website%2Clocale.en_US%2Ctitle.Fuzzy%20Freak%2Cdescription.Celebrity%20News%20and%20Gossip%2Curl.http%3A%2F%2Fwww%252Efuzzyfreak%252Ecom
28 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
4 ms
iframe.html
29 ms
facebook-white-60.png
36 ms
shares.json
58 ms
links.getStats
150 ms
links.getStats
232 ms
count.json
58 ms
button_info.json
49 ms
yum-count
56 ms
facebooklike-white-60.png
11 ms
twitter-white-60.png
10 ms
googleplus-white-60.png
16 ms
pinterest-white-60.png
14 ms
email-white-60.png
13 ms
sumome-white-60.png
13 ms
share
50 ms
jsonpcallback
215 ms
jsonpcallback
225 ms
jsonpcallback
280 ms
jsonpcallback
297 ms
rpc
94 ms
jsonpcallback
321 ms
101 ms
blank.html
0 ms
echo.htm
212 ms
jsonpcallback
314 ms
jsonpcallback
339 ms
jsonpcallback
333 ms
ui
39 ms
aa.js
161 ms
p.js
95 ms
fuzzyfreak.com accessibility score
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
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
Links do not have a discernible name
fuzzyfreak.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
fuzzyfreak.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fuzzyfreak.com 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 English. Our system also found out that Fuzzyfreak.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.
fuzzyfreak.com
Open Graph data is detected on the main page of Fuzzyfreak. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: