13 sec in total
1.2 sec
11.5 sec
328 ms
Welcome to fayean.com homepage info - get ready to check Fayean best content right away, or after learning these important things about fayean.com
Established in 1986, FAYEAN sport is committed to providing each customer the highest quality outdoor and sports product. Our products have been exported to over 30 countries, such as Germany, USA, Au...
Visit fayean.comWe analyzed Fayean.com page load time and found that the first response time was 1.2 sec and then it took 11.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fayean.com performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value22.5 s
0/100
25%
Value28.1 s
0/100
10%
Value26,260 ms
0/100
30%
Value0.078
95/100
15%
Value39.2 s
0/100
10%
1168 ms
769 ms
93 ms
654 ms
835 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Fayean.com, 31% (19 requests) were made to A3.leadongcdn.com and 31% (19 requests) were made to A0.leadongcdn.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source A2.leadongcdn.com.
Page size can be reduced by 63.3 kB (77%)
81.8 kB
18.4 kB
In fact, the total size of Fayean.com main page is 81.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 72.6 kB which makes up the majority of the site volume.
Potential reduce by 57.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. 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 57.0 kB or 79% of the original size.
Potential reduce by 6.3 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 6.3 kB or 69% of the original size.
Number of requests can be reduced by 23 (40%)
58
35
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fayean. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.fayean.com
1168 ms
3oirKBcg6fRfiSmlkmokokkriil.css
769 ms
ijiiKB36y6SRlimmkkkoroikdk.css
93 ms
7oiiKBd13fRyiSmlkmokokkriil.css
654 ms
yjirKBx88yRfiSmlkmokokkriil.css
835 ms
fkijKBvytaRaiSmlkmokokkriil.css
609 ms
hiijKBctdhRciSmlkmokokkriil.css
760 ms
bmirKBace3RaiSmlkmokokkriil.css
794 ms
jquery-1.11.0.min.js
28 ms
tjijKBdhe6ReiSmlkmokokkriil.js
756 ms
style.css
512 ms
css
45 ms
style_9.css
776 ms
bmiiKBza51RhiSrnilnpqnmroil.css
26 ms
xkipKBeagxRciSmlkmokokkriik.js
120 ms
dat.gui.js
662 ms
8rilKBd1t5RgiSmlkmokokkriil.js
2082 ms
uoijKBs2b2RgiSmlkmokokkriil.js
86 ms
6mikKBue2tRyiSmlkmokokkriil.js
1253 ms
ziikKB122uRsiSmlkmokokkriil.js
1235 ms
2qirKByteyRaiSmlkmokokkriil.js
438 ms
jquery.smartmenus.js
636 ms
1likKBx40tRxiSrnilnpqnmroil.js
757 ms
probe_3415_1.js
69 ms
sport-brac.jpg
3569 ms
back-brace.jpg
2994 ms
transholder.png
13 ms
neck-suppo-480-480.jpg
1353 ms
wrist-supp-480-480.jpg
1631 ms
knee-suppo-480-480.jpg
1424 ms
maternity--80-80.jpg
2193 ms
lumbar-sup-80-80.jpg
2790 ms
social-icons-c.png
21 ms
sport-brac.jpg
2952 ms
sport-supp.jpg
1724 ms
sport-brac.jpg
1042 ms
slimming-b-80-80.jpg
645 ms
lazyload-loading.gif
82 ms
medical-ba.jpg
1350 ms
back-corre-480-480.jpg
1939 ms
lumber-sup-480-480.jpg
1954 ms
shoulder-s-480-480.jpg
11 ms
ankle-supp-480-480.jpg
1079 ms
elbow-supp-480-480.jpg
1527 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
33 ms
CLIMBING-S.jpg
3207 ms
menu_28.jpg
1930 ms
ABOUT-US_2.jpg
461 ms
ABOUT-US_2.jpg
2914 ms
fontawesome-webfont.woff
1598 ms
probe.js
381 ms
showBasket
1722 ms
skin.css
59 ms
sanjiao.png
1442 ms
sport-brac.png
1236 ms
back-suppo-640-640.jpg
1645 ms
knee-brace-640-640.jpg
1474 ms
neck-tract-640-640.jpg
782 ms
blank.gif
7 ms
skin.png
19 ms
loading.gif
5 ms
fayean.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.
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
fayean.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
fayean.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 Fayean.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 Fayean.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.
fayean.com
Open Graph description is not detected on the main page of Fayean. 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: