4.6 sec in total
354 ms
3.7 sec
509 ms
Welcome to fay.com homepage info - get ready to check Fay best content for Italy right away, or after learning these important things about fay.com
Visit Fay official website and discover iconic collections of designer men, women and children's clothing. Italian style combining quality, luxury and innovation.
Visit fay.comWe analyzed Fay.com page load time and found that the first response time was 354 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fay.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value18.6 s
0/100
25%
Value12.4 s
3/100
10%
Value4,180 ms
1/100
30%
Value0
100/100
15%
Value20.9 s
2/100
10%
354 ms
2278 ms
97 ms
119 ms
94 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 74% of them (55 requests) were addressed to the original Fay.com, 5% (4 requests) were made to F.vimeocdn.com and 4% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Fay.com.
Page size can be reduced by 2.2 MB (37%)
5.8 MB
3.6 MB
In fact, the total size of Fay.com main page is 5.8 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. 85% 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 4.2 MB which makes up the majority of the site volume.
Potential reduce by 79.2 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 79.2 kB or 80% of the original size.
Potential reduce by 850.7 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. Obviously, Fay needs image optimization as it can save up to 850.7 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 732.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 732.6 kB or 77% of the original size.
Potential reduce by 494.8 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. Fay.com needs all CSS files to be minified and compressed as it can save up to 494.8 kB or 89% of the original size.
Number of requests can be reduced by 38 (57%)
67
29
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
fay.com
354 ms
www.fay.com
2278 ms
jquery.js
97 ms
jquery-ui.min.js
119 ms
demo.css
94 ms
fay-style.css
116 ms
modernizr-2.6.2.min.js
24 ms
all.css
25 ms
jquery.bxslider.css
24 ms
update_hp.css
9 ms
jquery.bxslider.js
23 ms
update_hp.js
65 ms
advertising2016fay.css
25 ms
ADV2016.js
60 ms
font-awesome.min.css
41 ms
jquery.main.js
106 ms
infobubble-compiled.js
51 ms
js
102 ms
jquery.transit-0.9.9.min.js
139 ms
jquery.mobile.custom.min.js
73 ms
underscore.min.js
211 ms
selectivizr-min.js
80 ms
iscroll.js
100 ms
form-sender.min.js
100 ms
tooltip-nology.min.js
209 ms
search-nology.min.js
104 ms
zoom-nology.min.js
135 ms
store-locator.min.js
136 ms
lightbox-nology.min.js
136 ms
vimeo-player.min.js
137 ms
main-script.js
146 ms
global-slideshow-nology.min.js
234 ms
tools.min.js
137 ms
product-tools.min.js
136 ms
ga.js
33 ms
__utm.gif
12 ms
header-link-icon-store.png
13 ms
header-link-icon-mess.png
14 ms
fw17-thumb.jpg
48 ms
hp_fw17.jpg
46 ms
hp_2016_adv.jpg
235 ms
hp_2016_woman.jpg
44 ms
hp_2016_man.jpg
45 ms
woman-hp.jpg
13 ms
man-hp.jpg
45 ms
hp-adv-video.jpg
47 ms
dl02.jpg
233 ms
gtm.js
235 ms
nav-bg.png
279 ms
logo.png
412 ms
nav-separator.png
279 ms
subnav-bg.png
279 ms
bkg_nl_hp.png
613 ms
sprite.png
279 ms
footer-bg.png
439 ms
151497626
247 ms
ITCAvantGardeStd-Bk.woff
343 ms
ITCAvantGardeStd-XLt.woff
438 ms
ITCAvantGardeStd-Demi.woff
346 ms
0312a390-01c7-423e-ad0c-b5b4f25229af.woff
459 ms
bg-transparent.png
274 ms
fay-style.css
273 ms
c68f0543-0caf-4988-b234-355520476b8c.woff
331 ms
9151.js
120 ms
player.js
132 ms
player.css
79 ms
ga.js
97 ms
vuid.min.js
99 ms
__utm.gif
62 ms
proxy.html
35 ms
551256693.jpg
91 ms
cross-icon.png
113 ms
151497626
29 ms
__utm.gif
11 ms
fay.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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
fay.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
Missing source maps for large first-party JavaScript
fay.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
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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fay.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 Fay.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.
fay.com
Open Graph data is detected on the main page of Fay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: