Tools & Wizards About Us
wikifakebook.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wikifakebook.com

娱乐是一种态度

Page Load Speed

1.2 sec in total

First Response

234 ms

Resources Loaded

750 ms

Page Rendered

183 ms

wikifakebook.com screenshot

About Website

Visit wikifakebook.com now to see the best up-to-date Wikifakebook content and also check out these interesting facts you probably never knew about wikifakebook.com

WikiFakeBook is a FREE backing tracks software which play back backing music on the fly based on specified chord progression. User is able to specify desired chords and choose from hundreds of backing...

Visit wikifakebook.com

Key Findings

We analyzed Wikifakebook.com page load time and found that the first response time was 234 ms and then it took 933 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

wikifakebook.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

wikifakebook.com

234 ms

style.css

133 ms

x-click-but04.gif

78 ms

pixel.gif

80 ms

show_ads.js

19 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 48% of them (10 requests) were addressed to the original Wikifakebook.com, 19% (4 requests) were made to Pagead2.googlesyndication.com and 14% (3 requests) were made to Paypal.com. The less responsive or slowest element that took the longest time to load (361 ms) belongs to the original domain Wikifakebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.3 kB (20%)

Content Size

45.6 kB

After Optimization

36.3 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-59%

Potential reduce by 5.3 kB

  • Original 8.9 kB
  • After minification 7.5 kB
  • After compression 3.7 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 1.4 kB, which is 16% 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 5.3 kB or 59% of the original size.

JavaScript Optimization

-1%

Potential reduce by 184 B

  • Original 31.9 kB
  • After minification 31.8 kB
  • After compression 31.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.

CSS Optimization

-81%

Potential reduce by 3.9 kB

  • Original 4.8 kB
  • After minification 3.1 kB
  • After compression 933 B

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. Wikifakebook.com needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (20%)

Requests Now

20

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wikifakebook.com

wikifakebook.com

234 ms

style.css

style.css

133 ms

x-click-but04.gif

x-click-but04.gif

78 ms

pixel.gif

pixel.gif

80 ms

show_ads.js

show_ads.js

19 ms

x-click-but04.gif

x-click-but04.gif

39 ms

ca-pub-1820806278894898.js

ca-pub-1820806278894898.js

91 ms

zrt_lookup.html

zrt_lookup.html

84 ms

show_ads_impl.js

show_ads_impl.js

82 ms

ga.js

ga.js

29 ms

header_image.gif

header_image.gif

142 ms

header_background.gif

header_background.gif

324 ms

menu_1_bg.gif

menu_1_bg.gif

142 ms

menu_2_bg.gif

menu_2_bg.gif

142 ms

menu_3_bg.gif

menu_3_bg.gif

143 ms

menu_4_bg.gif

menu_4_bg.gif

142 ms

menu_5_bg.gif

menu_5_bg.gif

202 ms

WikiFakeBook-QuickGuide01.gif

WikiFakeBook-QuickGuide01.gif

361 ms

__utm.gif

__utm.gif

56 ms

ads

ads

288 ms

osd.js

osd.js

8 ms

Accessibility Review

wikifakebook.com accessibility score

66

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

wikifakebook.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

wikifakebook.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wikifakebook.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wikifakebook.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

wikifakebook.com

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