3 sec in total
180 ms
2.1 sec
790 ms
Welcome to fakebake.com homepage info - get ready to check Fake Bake best content for United States right away, or after learning these important things about fakebake.com
Get a radiant, natural-looking tan without the sun. See our full line of self-tanning formulas for every skin tone, for a fast-drying, streak-free and long lasting glow.
Visit fakebake.comWe analyzed Fakebake.com page load time and found that the first response time was 180 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fakebake.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value74.7 s
0/100
25%
Value49.3 s
0/100
10%
Value2,100 ms
7/100
30%
Value0.166
71/100
15%
Value47.3 s
0/100
10%
180 ms
68 ms
501 ms
300 ms
93 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Fakebake.com, 29% (26 requests) were made to Cdn11.bigcommerce.com and 12% (11 requests) were made to Cdn6.bigcommerce.com. The less responsive or slowest element that took the longest time to load (960 ms) relates to the external source Cdn6.bigcommerce.com.
Page size can be reduced by 460.2 kB (1%)
42.1 MB
41.7 MB
In fact, the total size of Fakebake.com main page is 42.1 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. 80% 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 41.8 MB which makes up the majority of the site volume.
Potential reduce by 180.0 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 59.4 kB, which is 28% 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 180.0 kB or 85% of the original size.
Potential reduce by 279.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. Fake Bake images are well optimized though.
Potential reduce by 1.2 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.
Number of requests can be reduced by 32 (42%)
77
45
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fake Bake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fakebake.com
180 ms
fakebake.com
68 ms
www.fakebake.com
501 ms
rtc6udd.js
300 ms
jquery.min.js
93 ms
theme-e25a42d0-c845-0137-3b46-0242ac110025.css
96 ms
css
98 ms
modernizr-custom.js
97 ms
js
118 ms
Bootstrap.js
90 ms
slick.min.css
90 ms
slick-theme.min.css
89 ms
slick.min.js
96 ms
getgeotrustsslseal
7 ms
theme-bundle.main.js
94 ms
csrf-protection-header-b572e5526f6854c73a5e080ef15a771f963740ae.js
103 ms
visitor_stencil.js
97 ms
ae3086d8243954183901234b2.js
134 ms
bigcommerce.js
95 ms
smile-bigcommerce.js
85 ms
platform.js
28 ms
fbevents.js
89 ms
hotjar-1715822.js
411 ms
events.js
476 ms
searchicon.png
558 ms
retail_logo_1486090185__19153_1486565186_1491842826.original.jpg
281 ms
basketicon.png
548 ms
accounticon.png
549 ms
homecelebcircle.jpg
659 ms
usp2.png
751 ms
usp3a.png
744 ms
homecat5.png
625 ms
inst.png
623 ms
fb.png
623 ms
tw.png
659 ms
yt.png
960 ms
Original_Is_Back.jpg
660 ms
Flawless_Lineup.jpg
664 ms
Bronzer_Brush_Combo.jpg
765 ms
Save_with_Kits.jpg
677 ms
loading.svg
359 ms
flawless-742a5616-m.jpg
454 ms
flawless-742a5616-new.jpg
454 ms
cosmeticsdsc00165-new.jpg
546 ms
body-mate-1-76.jpg.jpg
546 ms
product-line-742a6225-new.jpg
621 ms
product-line-742a6225.jpg
881 ms
serverComponent.php
260 ms
js
257 ms
analytics.js
409 ms
js
309 ms
i
215 ms
i
333 ms
embed.js
430 ms
ajax-loader.gif
183 ms
recent
401 ms
cookie-notification
154 ms
theme-bundle.chunk.16.js
424 ms
index.php
319 ms
442971119756649
218 ms
494 ms
i
125 ms
i
234 ms
i
336 ms
i
258 ms
slick.woff
125 ms
ec1ce18677284b1ad89d127f8298405a.js
178 ms
b91deb381a983463890df766160d0db7.js
249 ms
conversion_async.js
280 ms
modules.01a02f6e8b126e8c8358.js
225 ms
Flawless_Exfoliating_Wipes_Kit__05062.1614698305.jpg
217 ms
Flawless_Darker_Exfoliating_Wipes_Kit__12043.1614697183.jpg
230 ms
Exfoliating_Mitt__53138.1654800455.jpg
294 ms
Over_Achiever_Duo_Brush__66412.1637692837.jpg
293 ms
Airbrush_Mitt_Kit__39862.1617819590.jpg
294 ms
Airbrush_Exfoliating_Wipes_Kit__26917.1617819429.jpg
295 ms
Airbrush_Mistifier_Mitt_Kit__34264.1625085450.JPG
303 ms
Airbrush_Mistifier_Kit__90181.1617818288.jpg
301 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
172 ms
collect
79 ms
collect
109 ms
nobot
126 ms
ga-audiences
91 ms
127 ms
175 ms
iframe
25 ms
instashow.js
25 ms
iframe
22 ms
20 ms
18 ms
fakebake.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-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fakebake.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fakebake.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fakebake.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 Fakebake.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.
fakebake.com
Open Graph description is not detected on the main page of Fake Bake. 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: