Tools & Wizards About Us
francobuzz.com screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

francobuzz.com

域名到期-域名续费提醒

Page Load Speed

3 sec in total

First Response

414 ms

Resources Loaded

1.7 sec

Page Rendered

893 ms

francobuzz.com screenshot

About Website

Click here to check amazing Francobuzz content. Otherwise, check out these important facts you probably never knew about francobuzz.com

域名是企业重要的资产,您所访问的域名已经过期,请尽快联络注册商续费

Visit francobuzz.com

Key Findings

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

Performance Metrics

francobuzz.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.0 s

97/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.3 s

100/100

10%

Network Requests Diagram

francobuzz.com

414 ms

language-selector.css

30 ms

style.css

100 ms

css

28 ms

css

36 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 23% of them (15 requests) were addressed to the original Francobuzz.com, 23% (15 requests) were made to Scontent.xx.fbcdn.net and 15% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (414 ms) belongs to the original domain Francobuzz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.7 kB (50%)

Content Size

388.9 kB

After Optimization

195.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 50.9 kB

  • Original 63.0 kB
  • After minification 58.0 kB
  • After compression 12.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 50.9 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 8.9 kB

  • Original 91.4 kB
  • After minification 82.5 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. Francobuzz images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 57.7 kB

  • Original 144.9 kB
  • After minification 134.7 kB
  • After compression 87.2 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 57.7 kB or 40% of the original size.

CSS Optimization

-85%

Potential reduce by 76.3 kB

  • Original 89.6 kB
  • After minification 70.2 kB
  • After compression 13.3 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. Francobuzz.com needs all CSS files to be minified and compressed as it can save up to 76.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (58%)

Requests Now

59

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

francobuzz.com

francobuzz.com

414 ms

language-selector.css

language-selector.css

30 ms

style.css

style.css

100 ms

css

css

28 ms

css

css

36 ms

css

css

43 ms

scs.css

scs.css

45 ms

prettyPhoto.css

prettyPhoto.css

72 ms

jquery.min.js

jquery.min.js

34 ms

scs.js

scs.js

75 ms

launch.js

launch.js

49 ms

jquery-ui.min.js

jquery-ui.min.js

55 ms

modernizr.min.js

modernizr.min.js

65 ms

customscript.js

customscript.js

68 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

161 ms

sitepress.js

sitepress.js

162 ms

adsbygoogle.js

adsbygoogle.js

4 ms

widgets.js

widgets.js

165 ms

plusone.js

plusone.js

164 ms

all.js

all.js

104 ms

pattern3.png

pattern3.png

54 ms

francobuzz.png

francobuzz.png

112 ms

nav-arrow-down.png

nav-arrow-down.png

106 ms

star.png

star.png

107 ms

ca-pub-8795967677944137.js

ca-pub-8795967677944137.js

207 ms

zrt_lookup.html

zrt_lookup.html

98 ms

show_ads_impl.js

show_ads_impl.js

98 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

29 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

35 ms

5_80veqYtMg_mX_C_gEF_PesZW2xOQ-xsNqO47m55DA.ttf

5_80veqYtMg_mX_C_gEF_PesZW2xOQ-xsNqO47m55DA.ttf

93 ms

TJBgbd7QSbnZkQrnM77kmw.ttf

TJBgbd7QSbnZkQrnM77kmw.ttf

93 ms

guC5lwT5Dw7anV_xfpCGqw.ttf

guC5lwT5Dw7anV_xfpCGqw.ttf

92 ms

likebox.php

likebox.php

408 ms

187 ms

xd_arbiter.php

xd_arbiter.php

175 ms

xd_arbiter.php

xd_arbiter.php

231 ms

ads

ads

42 ms

likebox.php

likebox.php

183 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

16 ms

osd.js

osd.js

15 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

87 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

105 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

141 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

175 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

173 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

174 ms

11896022_1673219112892867_229548263283656934_n.jpg

11896022_1673219112892867_229548263283656934_n.jpg

167 ms

10858371_1574621159419330_4016280742321668410_n.png

10858371_1574621159419330_4016280742321668410_n.png

91 ms

12417600_1680610852213233_4631365824373735913_n.jpg

12417600_1680610852213233_4631365824373735913_n.jpg

93 ms

10448201_741878022537451_3979692970592113574_n.jpg

10448201_741878022537451_3979692970592113574_n.jpg

171 ms

12742177_1103273006372432_6977862442281573249_n.jpg

12742177_1103273006372432_6977862442281573249_n.jpg

91 ms

392379_100298416775112_1614733185_n.jpg

392379_100298416775112_1614733185_n.jpg

101 ms

12002052_174997256169898_5399728291633518761_n.jpg

12002052_174997256169898_5399728291633518761_n.jpg

142 ms

12360373_10203999259421557_3610787618173372917_n.jpg

12360373_10203999259421557_3610787618173372917_n.jpg

107 ms

11896022_1673219112892867_229548263283656934_n.jpg

11896022_1673219112892867_229548263283656934_n.jpg

159 ms

10429296_390430814455967_1402834979765763482_n.jpg

10429296_390430814455967_1402834979765763482_n.jpg

192 ms

10459146_799541416747012_7590124501287815198_n.jpg

10459146_799541416747012_7590124501287815198_n.jpg

137 ms

12645047_1707002306182651_2552089846137651825_n.jpg

12645047_1707002306182651_2552089846137651825_n.jpg

145 ms

1379841_10150004552801901_469209496895221757_n.jpg

1379841_10150004552801901_469209496895221757_n.jpg

154 ms

12279135_1208848772500220_1647505692097661862_n.jpg

12279135_1208848772500220_1647505692097661862_n.jpg

288 ms

11214088_367022903491157_4071892754392402455_n.jpg

11214088_367022903491157_4071892754392402455_n.jpg

194 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

44 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

42 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

21 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

36 ms

ping

ping

73 ms

Accessibility Review

francobuzz.com accessibility score

96

Accessibility Issues

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

francobuzz.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

francobuzz.com SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document uses plugins

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Francobuzz.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed French language. Our system also found out that Francobuzz.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

francobuzz.com

Open Graph description is not detected on the main page of Francobuzz. 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: