Tools & Wizards About Us
epicfakes.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

epicfakes.com

Scannable Fake Driver's Licenses - How To Buy Fake ID - EpicFakes

Page Load Speed

1.7 sec in total

First Response

291 ms

Resources Loaded

1.2 sec

Page Rendered

183 ms

epicfakes.com screenshot

About Website

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

Most popular scannable fake ids complete with all security features. Webs largest scannable fake id selection. More people buy fake ids here than anywhere else. Effective ID designs. Fast and Free shi...

Visit epicfakes.com

Key Findings

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

Performance Metrics

epicfakes.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.275

44/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

epicfakes.com

291 ms

bootstrap.css

206 ms

animate.css

170 ms

font-awesome.css

171 ms

nexus.css

254 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 82% of them (23 requests) were addressed to the original Epicfakes.com, 7% (2 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (852 ms) belongs to the original domain Epicfakes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.8 kB (12%)

Content Size

610.7 kB

After Optimization

534.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 17.5 kB

  • Original 21.1 kB
  • After minification 12.4 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 8.8 kB, which is 41% 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 17.5 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 13.5 kB

  • Original 436.0 kB
  • After minification 422.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. Epic Fakes images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 30.1 kB

  • Original 103.7 kB
  • After minification 103.7 kB
  • After compression 73.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 30.1 kB or 29% of the original size.

CSS Optimization

-30%

Potential reduce by 14.7 kB

  • Original 49.8 kB
  • After minification 49.8 kB
  • After compression 35.1 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. Epicfakes.com needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 30% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epicfakes.com

epicfakes.com

291 ms

bootstrap.css

bootstrap.css

206 ms

animate.css

animate.css

170 ms

font-awesome.css

font-awesome.css

171 ms

nexus.css

nexus.css

254 ms

responsive.css

responsive.css

173 ms

css

css

21 ms

jquery.min.js

jquery.min.js

418 ms

bootstrap.min.js

bootstrap.min.js

284 ms

scripts.js

scripts.js

284 ms

jquery.isotope.js

jquery.isotope.js

455 ms

jquery.slicknav.js

jquery.slicknav.js

292 ms

jquery.visible.js

jquery.visible.js

335 ms

jquery.sticky.js

jquery.sticky.js

351 ms

slimbox2.js

slimbox2.js

347 ms

modernizr.custom.js

modernizr.custom.js

384 ms

counter.js

counter.js

29 ms

slide1.jpg

slide1.jpg

847 ms

slide2.jpg

slide2.jpg

852 ms

image2.jpg

image2.jpg

526 ms

index_5.jpg

index_5.jpg

562 ms

image1.jpg

image1.jpg

524 ms

tick.png

tick.png

302 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XljLdSL57k.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XljLdSL57k.ttf

8 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5XljLdSL57k.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5XljLdSL57k.ttf

15 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

326 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

592 ms

t.php

t.php

85 ms

Accessibility Review

epicfakes.com accessibility score

72

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

epicfakes.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

epicfakes.com SEO score

92

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

Image elements do not have [alt] attributes

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 Epicfakes.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 Epicfakes.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

epicfakes.com

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