3.3 sec in total
572 ms
2.2 sec
550 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 572 ms and then it took 2.7 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.6 s
31/100
10%
Value17.0 s
0/100
25%
Value9.8 s
10/100
10%
Value1,770 ms
10/100
30%
Value0.164
72/100
15%
Value17.5 s
4/100
10%
572 ms
95 ms
132 ms
45 ms
106 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 48% of them (29 requests) were addressed to the original Fakebake.com, 30% (18 requests) were made to Cdn.shopify.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (804 ms) relates to the external source Customerapp.anncode.com.
Page size can be reduced by 356.2 kB (17%)
2.1 MB
1.7 MB
In fact, the total size of Fakebake.com main page is 2.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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 346.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. 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 346.7 kB or 80% of the original size.
Potential reduce by 3.3 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 634 B
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.
Potential reduce by 5.5 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. Fakebake.com has all CSS files already compressed.
Number of requests can be reduced by 29 (62%)
47
18
The browser has sent 47 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 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fakebake.com
572 ms
css2
95 ms
css
132 ms
vendor.min.css
45 ms
theme-styles.css
106 ms
theme-styles-responsive.css
70 ms
theme-settings.css
81 ms
jquery.min.js
94 ms
jquery-cookie.min.js
99 ms
lazysizes.min.js
100 ms
preloads.js
272 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
269 ms
storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js
270 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
268 ms
selectors.js
125 ms
smile-loader.js
276 ms
easylocation-storefront.min.js
273 ms
cart.js
271 ms
form-builder-script.js
267 ms
js
270 ms
css2
252 ms
helper.js
102 ms
vendor.min.js
249 ms
api.jquery.js
241 ms
option_selection-86cdd286ddf3be7e25d68b9fc5965d7798a3ff6228ff79af67b3f4e41d6a34be.js
251 ms
jquery.sticky.js
252 ms
halo.js
253 ms
template7.js
241 ms
javascript
246 ms
ac-tiered-style.css
244 ms
trekkie.storefront.99bdfbca815ea24ab1705979a783df6e7810b51d.min.js
126 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
127 ms
shopify-boomerang-1.0.0.min.js
123 ms
Fake-Bake-Logo---LPA-white.png
89 ms
retail_logo.webp
89 ms
Bronze-shutterstock_1681180837.jpg
86 ms
Flawless_Review_Slide_1200x.jpg
87 ms
Airbrush_Review_Slide_1200x.jpg
129 ms
Flawless_Darker_Review_Slide_1200x.jpg
90 ms
Flawless_Mousse_Review_Slide_cd155a76-a078-471d-8556-69b56afefb37_1200x.jpg
89 ms
Tanning_Water_Review_Slide_cfe806f2-ec4a-4a68-8cb4-8e59276e1dae_1200x.jpg
130 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODH7alwQ.woff
92 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDH7alwQ.woff
143 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EH7alwQ.woff
144 ms
u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwQ.woff
144 ms
fa-v4compatibility.ttf
79 ms
fa-regular-400.ttf
79 ms
fa-brands-400.ttf
79 ms
fa-solid-900.ttf
114 ms
fa.woff
77 ms
fontawesome-webfont.woff
158 ms
Flawless-Slider-FkB-2023-12-D1.jpg
63 ms
Slider-Home-Top-Celebrity-Circle-D5.jpg
29 ms
ping
377 ms
fa.ttf
51 ms
fontawesome-webfont.ttf
64 ms
fa.svg
97 ms
ac-tiered-qty-product.js
775 ms
ac-tiered-qty-cart.js
804 ms
update.json
254 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 data is detected on the main page of Fake Bake. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: