Tools & Wizards About Us
fakeapp.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

fakeapp.com

Fake - Mac OS X Web Browser Automation and Webapp Testing Made Simple.

Page Load Speed

727 ms in total

First Response

115 ms

Resources Loaded

531 ms

Page Rendered

81 ms

fakeapp.com screenshot

About Website

Visit fakeapp.com now to see the best up-to-date Fake App content for India and also check out these interesting facts you probably never knew about fakeapp.com

Fake is a new browser for Mac OS X that makes web automation simple. Fake allows you to drag discreet browser Actions into a graphical Workflow that can be run again and again without human interactio...

Visit fakeapp.com

Key Findings

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

Performance Metrics

fakeapp.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

fakeapp.com

115 ms

fakeapp.com

144 ms

mootools.js

32 ms

swfobject.js

63 ms

videobox.js

91 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 84% of them (26 requests) were addressed to the original Fakeapp.com, 6% (2 requests) were made to Ssl.google-analytics.com and 3% (1 request) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (144 ms) belongs to the original domain Fakeapp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.3 kB (18%)

Content Size

146.5 kB

After Optimization

120.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fakeapp.com main page is 146.5 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. 15% of websites need less resources to load. Images take 118.6 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 6.6 kB

  • Original 9.3 kB
  • After minification 7.3 kB
  • After compression 2.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 2.0 kB, which is 22% 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 6.6 kB or 71% of the original size.

Image Optimization

-16%

Potential reduce by 19.5 kB

  • Original 118.6 kB
  • After minification 99.1 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, Fake App needs image optimization as it can save up to 19.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-9%

Potential reduce by 129 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 1.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. Fakeapp.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fake App. According to our analytics all requests are already optimized.

Network Requests Diagram

fakeapp.com

fakeapp.com

115 ms

fakeapp.com

fakeapp.com

144 ms

mootools.js

mootools.js

32 ms

swfobject.js

swfobject.js

63 ms

videobox.js

videobox.js

91 ms

videobox.css

videobox.css

94 ms

style.css

style.css

99 ms

14697494

14697494

126 ms

fluidium_logo_icon.png

fluidium_logo_icon.png

64 ms

buy_button.png

buy_button.png

63 ms

play_icon.png

play_icon.png

62 ms

shapes_banner2.png

shapes_banner2.png

65 ms

ga.js

ga.js

22 ms

top_bg.png

top_bg.png

55 ms

tagline.png

tagline.png

56 ms

menu_bg.png

menu_bg.png

65 ms

home_button_hover.png

home_button_hover.png

67 ms

dload_button.png

dload_button.png

81 ms

column.png

column.png

82 ms

home_button.png

home_button.png

89 ms

blog_button.png

blog_button.png

93 ms

dev_button.png

dev_button.png

96 ms

about_button.png

about_button.png

98 ms

blog_button_hover.png

blog_button_hover.png

110 ms

dev_button_hover.png

dev_button_hover.png

114 ms

about_button_hover.png

about_button_hover.png

120 ms

dload_button_hover.png

dload_button_hover.png

124 ms

buy_button_hover.png

buy_button_hover.png

129 ms

__utm.gif

__utm.gif

12 ms

pixel.gif

pixel.gif

18 ms

87270625-a961e0d9123b78316874f5f2de2176ae9e6a206dfaa66b900301dfa01e8c4e40-d

87270625-a961e0d9123b78316874f5f2de2176ae9e6a206dfaa66b900301dfa01e8c4e40-d

63 ms

Accessibility Review

fakeapp.com accessibility score

88

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

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

fakeapp.com best practices score

67

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

fakeapp.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fakeapp.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fakeapp.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

fakeapp.com

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