1.6 sec in total
261 ms
980 ms
342 ms
Click here to check amazing FEETNESS content for Armenia. Otherwise, check out these important facts you probably never knew about feetness.co
Discover the most advanced technologies in footcare with our comfortable and trendy collections from Scholl, Kickers, Babybotte and more in stores & on feetness.co
Visit feetness.coWe analyzed Feetness.co page load time and found that the first response time was 261 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
feetness.co performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value18.6 s
0/100
25%
Value7.6 s
25/100
10%
Value420 ms
66/100
30%
Value1.695
0/100
15%
Value12.5 s
14/100
10%
261 ms
47 ms
48 ms
147 ms
78 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 97% of them (68 requests) were addressed to the original Feetness.co, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (494 ms) belongs to the original domain Feetness.co.
Page size can be reduced by 156.7 kB (6%)
2.8 MB
2.6 MB
In fact, the total size of Feetness.co main page is 2.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. 70% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 58.9 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 16.0 kB, which is 23% 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 58.9 kB or 85% of the original size.
Potential reduce by 14.0 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. FEETNESS images are well optimized though.
Potential reduce by 26.8 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 26.8 kB or 14% of the original size.
Potential reduce by 57.0 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. Feetness.co needs all CSS files to be minified and compressed as it can save up to 57.0 kB or 60% of the original size.
Number of requests can be reduced by 27 (42%)
65
38
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEETNESS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
261 ms
jquery_ui_datepicker.css
47 ms
jquery_ui_theme.css
48 ms
js
147 ms
bootstrap.min.css
78 ms
website.css
59 ms
font-awesome.css
62 ms
fullpage.css
74 ms
fancybox.css
75 ms
animate.css
87 ms
slick.css
84 ms
slick-theme.css
128 ms
fbevents.js
40 ms
flashdownwhite.png
75 ms
cartw.png
92 ms
locator.png
92 ms
logo.png
91 ms
glass.png
92 ms
cart.png
94 ms
responsive.png
93 ms
138_background.jpg
236 ms
86_background.jpg
237 ms
88_background.jpg
253 ms
89_background.jpg
244 ms
23_homecollection.jpg
173 ms
22_homecollection.jpg
172 ms
24_homecollection_2.jpg
174 ms
star.png
178 ms
CAPLD-2542821BLK.jpg
180 ms
jquery.js
227 ms
jquerymigrate.js
494 ms
parallax.js
240 ms
slimscroll.min.js
240 ms
fullpage.js
262 ms
functions.js
252 ms
jcycle.js
258 ms
bgpos.js
249 ms
jquery.easing.min.js
248 ms
fancybox.js
281 ms
jwplayer.js
279 ms
slick.js
286 ms
notification.css
284 ms
notification.js
284 ms
jqueryui.js
332 ms
accordion.js
300 ms
ddslick.js
298 ms
KC10-KKBUBBLOKAYL.jpg
321 ms
SHLD-BROOKLNLWTPN.jpg
294 ms
SHLD-MILLENMAANBL.jpg
258 ms
25_homecollectionlarge.jpg
265 ms
s1.png
262 ms
s2.png
279 ms
s3.png
282 ms
b1.png
283 ms
b2.png
284 ms
Gill%20Sans%20MT%20Book.woff
288 ms
b3.png
212 ms
logos.png
215 ms
fb1.png
211 ms
insta1.png
213 ms
opa1.png
186 ms
opa.png
178 ms
fontawesome-webfont.woff
187 ms
Expansiva.woff
180 ms
smallemail.jpg
180 ms
payment.png
189 ms
slickleftw.png
30 ms
slickrightw.png
39 ms
ajax-loader.gif
37 ms
slick.woff
31 ms
feetness.co 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
feetness.co 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
feetness.co SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feetness.co can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Feetness.co 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.
feetness.co
Open Graph description is not detected on the main page of FEETNESS. 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: