6.9 sec in total
2 sec
4.4 sec
501 ms
Visit fakemillion.com now to see the best up-to-date Fake Million content for United States and also check out these interesting facts you probably never knew about fakemillion.com
The story of Fake Million and how to get the one million dollar bill. Founding information about the company and owners.
Visit fakemillion.comWe analyzed Fakemillion.com page load time and found that the first response time was 2 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fakemillion.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value6.5 s
9/100
25%
Value10.2 s
8/100
10%
Value1,730 ms
10/100
30%
Value0.077
95/100
15%
Value20.9 s
2/100
10%
2013 ms
38 ms
137 ms
134 ms
91 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 54% of them (69 requests) were addressed to the original Fakemillion.com, 9% (12 requests) were made to Fonts.gstatic.com and 6% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Fakemillion.com.
Page size can be reduced by 1.3 MB (38%)
3.5 MB
2.1 MB
In fact, the total size of Fakemillion.com main page is 3.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 61.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 61.1 kB or 81% of the original size.
Potential reduce by 4.6 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 Million images are well optimized though.
Potential reduce by 893.0 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 893.0 kB or 68% of the original size.
Potential reduce by 357.6 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. Fakemillion.com needs all CSS files to be minified and compressed as it can save up to 357.6 kB or 71% of the original size.
Number of requests can be reduced by 66 (60%)
110
44
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fake Million. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
fakemillion.com
2013 ms
css
38 ms
wp-emoji-release.min.js
137 ms
styles.css
134 ms
woocommerce-layout.css
91 ms
woocommerce.css
126 ms
modal.css
123 ms
certificate-modal.css
146 ms
style.css
248 ms
css
15 ms
css
26 ms
superfish.css
184 ms
component.css
182 ms
font-awesome.min.css
192 ms
jquery.fancybox.css
252 ms
flexslider.css
286 ms
style-responsive.css
274 ms
style-custom.css
272 ms
gdlr-woocommerce.css
300 ms
font-awesome.min.css
338 ms
jquery.js
412 ms
jquery-migrate.min.js
332 ms
analytics.js
57 ms
logo.png
65 ms
icon-search.png
61 ms
facebook.png
60 ms
google-plus.png
62 ms
twitter.png
65 ms
pinterest.png
105 ms
reddit.png
104 ms
stumble-upon.png
106 ms
digg.png
120 ms
cta-background.png
319 ms
cta-traditional-million.png
484 ms
best-seller-badge.png
239 ms
IgZJs4-7SA1XX_edsoXWog.ttf
47 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
63 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
89 ms
k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf
92 ms
EInbV5DfGHOiMmvb1Xr-hi3USBnSvpkopQaUR-2r7iU.ttf
92 ms
SHXJdWnWW6HDq-6DpcG8Py3USBnSvpkopQaUR-2r7iU.ttf
106 ms
fontawesome-webfont.woff
259 ms
fontawesome-webfont.woff
185 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
54 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
67 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
75 ms
collect
13 ms
nm088-Traditional-Million-Both1-500x429.jpg
275 ms
nm402-RHPS-Both1-500x453.jpg
278 ms
nm332-Autism-Both1-500x427.jpg
241 ms
nm220-Support-our-Troops-both1-500x451.jpg
285 ms
nm320-Nightmare-Before-Xmas-Both1-500x433.jpg
241 ms
nm302-Vampire-Both1-500x446.jpg
269 ms
nm305-Witch-Both1-500x451.jpg
432 ms
nm408-Zelda-Both1-500x442.jpg
463 ms
nm367-Harry-Potter-Both1-500x449.jpg
454 ms
nm322-Cow-Both1-500x415.jpg
435 ms
nm088-Traditional-Million-Both1-250x215.jpg
455 ms
nm237-Modern-Santa-Both1-250x228.jpg
504 ms
nm287-Billion-Dollar-Both1-250x219.jpg
515 ms
nm311-John-Lennon-Both1-250x218.jpg
561 ms
nm320-Nightmare-Before-Xmas-Both1-250x217.jpg
516 ms
nm333-Trillion-Both1-250x224.jpg
604 ms
adsbygoogle.js
17 ms
ca-pub-5133568895519915.js
75 ms
zrt_lookup.html
34 ms
show_ads_impl.js
36 ms
scripts.js
497 ms
add-to-cart.min.js
497 ms
jquery.blockUI.min.js
550 ms
js.cookie.min.js
552 ms
woocommerce.min.js
531 ms
cart-fragments.min.js
551 ms
superfish.js
555 ms
hoverIntent.min.js
600 ms
modernizr.custom.js
590 ms
jquery.dlmenu.js
611 ms
jquery.easing.js
590 ms
jquery.fancybox.pack.js
592 ms
jquery.fancybox-media.js
609 ms
jquery.fancybox-thumbs.js
651 ms
jquery.flexslider.min.js
648 ms
gdlr-script.js
656 ms
wp-embed.min.js
666 ms
api.js
73 ms
ads
210 ms
osd.js
14 ms
ads
214 ms
gen_204
15 ms
ad
39 ms
o16FtOAn.js
25 ms
m_window_focus_non_hydra.js
27 ms
osd_listener.js
28 ms
m_qs_click_protection.js
31 ms
abg.js
3 ms
lidar.js
56 ms
d5qAyLYU.js
54 ms
pixel
43 ms
i_all_aol2.js
54 ms
transparent.png
26 ms
pixel
70 ms
pixel
71 ms
9im3l02I.html
19 ms
fpJ246J2fJ0bYHH6KdX6NZQGrKMRoryxUcO6omD8DP8.js
4 ms
polyfills.promise.js
21 ms
polyfills.intersection-observer.js
21 ms
stormtrooper.css
21 ms
vast.js
18 ms
jwpsrv.js
17 ms
related.js
19 ms
jwplayer.controls.js
17 ms
sync
29 ms
recaptcha__en.js
86 ms
fakemillion.com
1678 ms
ajax-loader.gif
60 ms
anchor
27 ms
styles__ltr.css
4 ms
n7H2Os8-eFxQ6zQNHIhDfXM6vSVF9a2hvt8h4-tkJxY.js
16 ms
webworker.js
19 ms
logo_48.png
13 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
17 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
20 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
27 ms
bframe
21 ms
recaptcha__en.js
11 ms
recaptcha__en.js
8 ms
woocommerce-smallscreen.css
65 ms
fakemillion.com accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
fakemillion.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fakemillion.com SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fakemillion.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 Fakemillion.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.
fakemillion.com
Open Graph data is detected on the main page of Fake Million. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: