Tools & Wizards About Us
funaze.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

funaze.com

FUNAZE.COM

Page Load Speed

3.2 sec in total

First Response

357 ms

Resources Loaded

2.5 sec

Page Rendered

359 ms

funaze.com screenshot

About Website

Welcome to funaze.com homepage info - get ready to check FUNAZE best content for India right away, or after learning these important things about funaze.com

Forsale Lander

Visit funaze.com

Key Findings

We analyzed Funaze.com page load time and found that the first response time was 357 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

funaze.com performance score

0

Network Requests Diagram

www.funaze.com

357 ms

wp-emoji-release.min.js

80 ms

form_style.css

157 ms

font-awesome.min.css

161 ms

bootstrap.min.css

250 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 35% of them (32 requests) were addressed to the original Funaze.com, 22% (20 requests) were made to Static.xx.fbcdn.net and 10% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (622 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 904.4 kB (49%)

Content Size

1.8 MB

After Optimization

937.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Funaze.com main page is 1.8 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. 65% of websites need less resources to load. Javascripts take 863.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 152.4 kB

  • Original 194.0 kB
  • After minification 187.8 kB
  • After compression 41.6 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 152.4 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 15.5 kB

  • Original 592.3 kB
  • After minification 576.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. FUNAZE images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 577.5 kB

  • Original 863.5 kB
  • After minification 861.9 kB
  • After compression 286.0 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 577.5 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 159.1 kB

  • Original 191.7 kB
  • After minification 172.1 kB
  • After compression 32.6 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. Funaze.com needs all CSS files to be minified and compressed as it can save up to 159.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (54%)

Requests Now

81

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUNAZE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.funaze.com

www.funaze.com

357 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

80 ms

form_style.css

form_style.css

157 ms

font-awesome.min.css

font-awesome.min.css

161 ms

bootstrap.min.css

bootstrap.min.css

250 ms

style.css

style.css

163 ms

css

css

31 ms

flexslider.css

flexslider.css

162 ms

jquery.js

jquery.js

243 ms

jquery-migrate.min.js

jquery-migrate.min.js

229 ms

cntctfrm.js

cntctfrm.js

232 ms

scripts.js

scripts.js

234 ms

respond.min.js

respond.min.js

239 ms

b

b

10 ms

1.js

1.js

91 ms

addthis_widget.js

addthis_widget.js

15 ms

output.css

output.css

318 ms

navigation.js

navigation.js

319 ms

bootstrap.min.js

bootstrap.min.js

318 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

323 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

324 ms

awaken.slider.js

awaken.slider.js

324 ms

wp-embed.min.js

wp-embed.min.js

433 ms

ga.js

ga.js

50 ms

ontoplist31.png

ontoplist31.png

79 ms

v_92343.gif

v_92343.gif

80 ms

funaze_transparent-1.png

funaze_transparent-1.png

159 ms

predictNwin.jpg

predictNwin.jpg

343 ms

bingo-50.png

bingo-50.png

389 ms

xiaomiRedMi3.jpg

xiaomiRedMi3.jpg

158 ms

hijackBluff.jpg

hijackBluff.jpg

343 ms

eveTeasing.jpg

eveTeasing.jpg

345 ms

predictNwin-388x220.jpg

predictNwin-388x220.jpg

342 ms

bingo-50-388x220.png

bingo-50-388x220.png

386 ms

xiaomiRedMi3-388x220.jpg

xiaomiRedMi3-388x220.jpg

348 ms

hijackBluff-388x220.jpg

hijackBluff-388x220.jpg

382 ms

eveTeasing-388x220.jpg

eveTeasing-388x220.jpg

386 ms

msDhoni-388x220.jpg

msDhoni-388x220.jpg

414 ms

s.gif

s.gif

41 ms

likebox.php

likebox.php

409 ms

ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf

ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf

36 ms

toadOcfmlt9b38dHJxOBGGvd-IutAbwf5FQ8ZpuI2w4.ttf

toadOcfmlt9b38dHJxOBGGvd-IutAbwf5FQ8ZpuI2w4.ttf

50 ms

toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf

toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf

52 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

467 ms

gMhvhm-nVj1086DvGgmzB6CWcynf_cDxXwCLxiixG1c.ttf

gMhvhm-nVj1086DvGgmzB6CWcynf_cDxXwCLxiixG1c.ttf

113 ms

pFZGRS3ywNfpSqkEIed1Ww.ttf

pFZGRS3ywNfpSqkEIed1Ww.ttf

113 ms

b9QBgL0iMZfDSpmcXcE8nG9QJ2ZrAngtF2xl-5ukicw.ttf

b9QBgL0iMZfDSpmcXcE8nG9QJ2ZrAngtF2xl-5ukicw.ttf

48 ms

Zd2E9abXLFGSr9G3YK2MsB43XjeME5heavxWqLE69Ro.ttf

Zd2E9abXLFGSr9G3YK2MsB43XjeME5heavxWqLE69Ro.ttf

49 ms

__utm.gif

__utm.gif

22 ms

host.js

host.js

324 ms

collect

collect

250 ms

300lo.json

300lo.json

54 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

38 ms

tm-float-bg-right-bottom.png

tm-float-bg-right-bottom.png

21 ms

ajax

ajax

307 ms

trustedsite-reviews-tab-left.png

trustedsite-reviews-tab-left.png

12 ms

float2-right.png

float2-right.png

324 ms

McLpmVM3wCm.css

McLpmVM3wCm.css

182 ms

VH4VPudaxfN.css

VH4VPudaxfN.css

227 ms

6JjmkAGJU83.css

6JjmkAGJU83.css

272 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

378 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

401 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

306 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

307 ms

OloiM1PZafe.js

OloiM1PZafe.js

305 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

428 ms

1FCa-btixu2.js

1FCa-btixu2.js

423 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

422 ms

pObvZSrFc_4.js

pObvZSrFc_4.js

421 ms

Kt4tkgSRvHH.js

Kt4tkgSRvHH.js

423 ms

H3EKDTObx05.js

H3EKDTObx05.js

424 ms

eR-qA8bp1RM.js

eR-qA8bp1RM.js

424 ms

12715273_1613852455599796_4620303620199368227_n.jpg

12715273_1613852455599796_4620303620199368227_n.jpg

226 ms

12729272_1614275335557508_5439172241902330844_n.png

12729272_1614275335557508_5439172241902330844_n.png

517 ms

10354686_10150004552801856_220367501106153455_n.jpg

10354686_10150004552801856_220367501106153455_n.jpg

574 ms

12791091_128905160835462_791029002468610658_n.jpg

12791091_128905160835462_791029002468610658_n.jpg

611 ms

1379841_10150004552801901_469209496895221757_n.jpg

1379841_10150004552801901_469209496895221757_n.jpg

615 ms

12439240_200307556985756_5873300081482552510_n.jpg

12439240_200307556985756_5873300081482552510_n.jpg

621 ms

12803039_157106741345802_4560581598481759958_n.jpg

12803039_157106741345802_4560581598481759958_n.jpg

621 ms

10423306_368872433317828_2939997609621641766_n.jpg

10423306_368872433317828_2939997609621641766_n.jpg

620 ms

12032275_1049448608406437_2041512616197084762_n.jpg

12032275_1049448608406437_2041512616197084762_n.jpg

622 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

137 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

138 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

42 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

8 ms

fql

fql

130 ms

count.json

count.json

46 ms

info.json

info.json

37 ms

shares.json

shares.json

23 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

42 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

85 ms

SEO Factors

funaze.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funaze.com 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 Funaze.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.

Social Sharing Optimization

funaze.com

Open Graph data is detected on the main page of FUNAZE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: