22.4 sec in total
440 ms
21.3 sec
742 ms
Click here to check amazing Faburnails content. Otherwise, check out these important facts you probably never knew about faburnails.com
Visit faburnails.comWe analyzed Faburnails.com page load time and found that the first response time was 440 ms and then it took 22 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
faburnails.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value5.7 s
16/100
25%
Value14.9 s
1/100
10%
Value10 ms
100/100
30%
Value0.839
4/100
15%
Value8.4 s
39/100
10%
440 ms
749 ms
186 ms
169 ms
165 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original Faburnails.com, 51% (33 requests) were made to D13z1xw8270sfc.cloudfront.net and 37% (24 requests) were made to D11fdyfhxcs9cr.cloudfront.net. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Gfx-elb.fw1.biz.
Page size can be reduced by 241.5 kB (10%)
2.3 MB
2.1 MB
In fact, the total size of Faburnails.com main page is 2.3 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. 40% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 40.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 40.1 kB or 85% of the original size.
Potential reduce by 150.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. Faburnails images are well optimized though.
Potential reduce by 29.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 29.0 kB or 76% of the original size.
Potential reduce by 22.3 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. Faburnails.com needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 65% of the original size.
Number of requests can be reduced by 16 (26%)
61
45
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faburnails. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
faburnails.com
440 ms
www.faburnails.com
749 ms
jquery.min.js
186 ms
basketajax2.1.6.js
169 ms
accounting.min.js
165 ms
jquery.simplemodal.1.4.4.min.js
168 ms
290072-v79-mh_static_grunge14.css
270 ms
style.css
158 ms
responsive_nav_v4.js
160 ms
nivo-sliderv2.css
165 ms
default.css
311 ms
jquery.nivo.slider.pack.js
755 ms
default.aspx
282 ms
290072_635384887729010137_logo.png
160 ms
button_details.png
345 ms
button_addtocart.png
81 ms
paypal01.gif
89 ms
headline-new.png
1261 ms
goodies.png
3005 ms
pixx.jpg
440 ms
pix-2.jpg
382 ms
pix-3.jpg
403 ms
&no_shipping=1
295 ms
&no_shipping=1
333 ms
SOLD%20OUT&no_shipping=1
379 ms
&no_shipping=1
555 ms
&no_shipping=1
453 ms
&no_shipping=1
434 ms
&no_shipping=1
860 ms
&no_shipping=1
556 ms
&no_shipping=1
604 ms
&no_shipping=1
578 ms
&no_shipping=1
706 ms
&no_shipping=1
676 ms
SOLD%20OUT&no_shipping=1
1509 ms
&no_shipping=1
742 ms
&no_shipping=1
760 ms
&no_shipping=1
813 ms
&no_shipping=1
862 ms
&no_shipping=1
965 ms
&no_shipping=1
1757 ms
&no_shipping=1
1225 ms
&no_shipping=1
1097 ms
&no_shipping=1
1252 ms
&no_shipping=1
1528 ms
SOLD%20OUT&no_shipping=1
1358 ms
&no_shipping=1
1844 ms
SOLD%20OUT&no_shipping=1
1857 ms
&no_shipping=1
2122 ms
bgshape_topleft.png
346 ms
bgshape_mainleft.png
80 ms
bgshape_topright.png
144 ms
bgshape_mainright.png
110 ms
bgshape_main.png
124 ms
navleft_arrow_start.png
144 ms
navleft_arrow_line.png
169 ms
navleft_arrow_end.png
179 ms
default.aspx
19511 ms
loading.gif
80 ms
title_overlay.png
627 ms
bg_prodbox.png
786 ms
bgshape_bottomleft.png
66 ms
bgshape_bottomright.png
650 ms
MyAccountLogin
181 ms
www.faburnails.com
912 ms
faburnails.com accessibility score
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
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
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.
faburnails.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faburnails.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Faburnails.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.
faburnails.com
Open Graph description is not detected on the main page of Faburnails. 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: