Tools & Wizards About Us
fake-it.to screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fake-it.to

ᐅ Fake IT - Fake the World | Fake Name & IBAN / Credit Card Generator

Page Load Speed

1.9 sec in total

First Response

28 ms

Resources Loaded

1.4 sec

Page Rendered

474 ms

fake-it.to screenshot

About Website

Click here to check amazing Fake IT content for Germany. Otherwise, check out these important facts you probably never knew about fake-it.to

Fake IT ➤ Fake Generator / Calculator for: Names ✅ Addresses ✅ Credit Cards ✅ IBAN Number ✅ Fake Mail ✅ Username ✅ Password ✅ and more ✅ real algorithms ✅

Visit fake-it.to

Key Findings

We analyzed Fake-it.to page load time and found that the first response time was 28 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

fake-it.to performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

fake-it.to

28 ms

outputter.io

393 ms

style.css

16 ms

js

64 ms

js

124 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fake-it.to, 57% (21 requests) were made to Outputter.io and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (524 ms) relates to the external source Outputter.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.8 kB (8%)

Content Size

899.6 kB

After Optimization

824.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fake-it.to main page is 899.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. 65% of websites need less resources to load. Images take 728.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.8 kB

  • Original 36.1 kB
  • After minification 36.1 kB
  • After compression 7.4 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 28.8 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 34.3 kB

  • Original 728.2 kB
  • After minification 693.9 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. Fake IT images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 11.8 kB

  • Original 135.4 kB
  • After minification 135.2 kB
  • After compression 123.6 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.

Requests Breakdown

Number of requests can be reduced by 14 (48%)

Requests Now

29

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fake-it.to

fake-it.to

28 ms

outputter.io

outputter.io

393 ms

style.css

style.css

16 ms

js

js

64 ms

js

js

124 ms

h.js

h.js

63 ms

adb_detect_pixfuture.js

adb_detect_pixfuture.js

37 ms

js.php

js.php

197 ms

splash.php

splash.php

144 ms

10c4a2a1f631d30a9b95f450cd22b1e4.js

10c4a2a1f631d30a9b95f450cd22b1e4.js

51 ms

879542f0a90adacc49786426fd7ade55.js

879542f0a90adacc49786426fd7ade55.js

75 ms

invoke.js

invoke.js

100 ms

invoke.js

invoke.js

102 ms

jquery.min.js

jquery.min.js

24 ms

jquery-ui.min.js

jquery-ui.min.js

31 ms

wow.min.js

wow.min.js

31 ms

owl.carousel.min.js

owl.carousel.min.js

32 ms

particles.min.js

particles.min.js

30 ms

scripts.js

scripts.js

342 ms

hotjar-2818667.js

hotjar-2818667.js

93 ms

SDK.js

SDK.js

68 ms

close-icon-circle.png

close-icon-circle.png

230 ms

fcount.php

fcount.php

414 ms

logo.svg

logo.svg

14 ms

outputter-startseite-header.png

outputter-startseite-header.png

10 ms

Outputter-Home-1000x667.jpg

Outputter-Home-1000x667.jpg

510 ms

FakeIT-Shop_300-250.gif

FakeIT-Shop_300-250.gif

15 ms

NordVPN-NextLevel-Banner-729x90.png

NordVPN-NextLevel-Banner-729x90.png

15 ms

Outputter_Premium_Banner_600-500.gif

Outputter_Premium_Banner_600-500.gif

109 ms

Outputter-Notebook-885x564.png

Outputter-Notebook-885x564.png

110 ms

Outputter-home-2.jpg

Outputter-home-2.jpg

524 ms

Kucoin-Banner-Option-4-Blue-Wave-BG-Single-Term-Advanced-crypto.gif

Kucoin-Banner-Option-4-Blue-Wave-BG-Single-Term-Advanced-crypto.gif

111 ms

outputter_premium_banner.gif

outputter_premium_banner.gif

112 ms

faq-home.png

faq-home.png

112 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

520 ms

main.js

main.js

25 ms

fcount.php

fcount.php

401 ms

Accessibility Review

fake-it.to accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Links do not have a discernible name

Best Practices

fake-it.to best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fake-it.to SEO score

93

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fake-it.to

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