4.7 sec in total
914 ms
3.6 sec
241 ms
Click here to check amazing Footsell content for South Korea. Otherwise, check out these important facts you probably never knew about footsell.com
나이키, 조던, 슈프림, 아디다스 이지부스트 스니커 및 스트릿 패션 커뮤니티
Visit footsell.comWe analyzed Footsell.com page load time and found that the first response time was 914 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
footsell.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.5 s
38/100
25%
Value5.8 s
50/100
10%
Value430 ms
64/100
30%
Value0.133
81/100
15%
Value6.0 s
64/100
10%
914 ms
591 ms
608 ms
407 ms
423 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 95% of them (56 requests) were addressed to the original Footsell.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Footsell.com.
Page size can be reduced by 255.2 kB (20%)
1.3 MB
1.1 MB
In fact, the total size of Footsell.com main page is 1.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. 30% of websites need less resources to load. Images take 940.6 kB which makes up the majority of the site volume.
Potential reduce by 42.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 42.0 kB or 79% of the original size.
Potential reduce by 6.9 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. Footsell images are well optimized though.
Potential reduce by 157.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 157.8 kB or 64% of the original size.
Potential reduce by 48.6 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. Footsell.com needs all CSS files to be minified and compressed as it can save up to 48.6 kB or 76% of the original size.
Number of requests can be reduced by 13 (23%)
56
43
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Footsell. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
footsell.com
914 ms
A.font-awesome.min.css.pagespeed.cf.RkZZMp5rvJ.css
591 ms
A.default.css.pagespeed.cf.h3u0Fz-255.css
608 ms
A.index.css.pagespeed.cf.b3hIOaNSy-.css
407 ms
A.pc.css.pagespeed.cf.yfqI5khWuO.css
423 ms
jquery-1.11.1.min.js.pagespeed.jm.YSzgc-BSX9.js
595 ms
jquery.ui.js.pagespeed.jm.Vp_dCgUvR4.js
276 ms
qtip2.js.pagespeed.jm.mlg2U3mni-.js
664 ms
functions.js.pagespeed.jm.TAcWRkCKA6.js
396 ms
default.js.pagespeed.jm.x76LIquOjB.js
407 ms
colorbox.js.pagespeed.jm.Ut0ZUeU7C9.js
419 ms
index.js.pagespeed.jm.IEeX2gVM4E.js
421 ms
eve2.js.pagespeed.jm.WcA_0t6cD2.js
787 ms
logo.png
380 ms
thumb_1456731464_3236d2884d97581d164630db1143b1f9.jpg
668 ms
jordan10.png
389 ms
jordan17.png
666 ms
jordan01.png
666 ms
jordan02.png
667 ms
jordanetc.png
667 ms
nike.png
748 ms
adidas.png
753 ms
jordan05.png
780 ms
thumb_1456800366_57358ae8b827fdc1ab87651e4af74348.jpg
789 ms
thumb_1456794283_1d61c50d6190f5a32d19c11b0b5077d5.jpg
1400 ms
thumb_1456789053_c542731218a9cc6b32f440593cfbdcd5.jpg
1059 ms
thumb_1456750005_40a89439aa80f76fa1fce298afb54cf2.jpg
1139 ms
thumb_1456746145_c4ef03c1ac4dd796ad21c035cf42439d.jpg
953 ms
thumb_1456742876_e52e36661cc7eb15b4281b6e0152c44f.jpg
1595 ms
thumb_1456737933_340bee7ae1310997b4841754fad69112.jpg
993 ms
thumb_1456737364_bf575b5597b319fce732fc29b8d62888.jpg
1153 ms
thumb_1448851481_18a7f7bcb411cbd793aacd2cf5a72e5f.jpg
1195 ms
thumb_1455777313_6a398b8e19074645b9402fb7f5e62d33.jpg
1270 ms
thumb_1456241175_edd80d0a1ad40cd7265038f69122b4e7.jpg
1336 ms
thumb_1455808932_fe739cfc21b14ca8afc364eef2ecb79e.jpg
1352 ms
thumb_1456143293_041e04145f4d86a78920bb2f8d637c81.jpg
1397 ms
thumb_1456802475_c02c37dfddb728ea6b03388620f36cc6.jpg
1483 ms
thumb_1455833853_bbacc73f3fdd334b3f93aaeb97a107ec.jpg
1532 ms
thumb_1456711797_6f4ba831b2a7ac3cfc1fb4bcb690dd5b.jpg
1552 ms
thumb_1456711778_a52bcecb35b5d3fdeab23ccb0c916bc1.jpg
1597 ms
thumb_1456800434_8841a3f01eb94ad0d493a582746067aa.jpg
1566 ms
fontawesome-webfont.woff
1873 ms
thumb_1455841273_eb3d162dc162c7a22bb3ad19b1c0db58.jpg
1572 ms
thumb_1455498447_d32c1bace13277abbcf0f455511d568a.jpg
1587 ms
thumb_1454546598_6925ab0b3e41f0e6acd94f12b5e295c8.jpg
1816 ms
thumb_1453857272_e2b4c81f672ff7ca224973cd20803293.jpg
1620 ms
analytics.js
22 ms
thumb_1453857240_14c33c8b18ce5341c8acf0c295f05d36.jpg
1631 ms
thumb_1453425847_75d6f140196fd926908f81f3abc84483.jpg
1744 ms
thumb_1453164976_ea2b30c4759eee81ef791a5513e02836.jpg
1568 ms
collect
13 ms
collect
61 ms
logo2.png
1579 ms
colorbox.css
1458 ms
jquery.qtip.css
1491 ms
evercookie_etag.php
1348 ms
evercookie_cache.php
1331 ms
evercookie_etag.php
814 ms
evercookie_cache.php
820 ms
footsell.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
footsell.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
footsell.com 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
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Footsell.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Footsell.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.
footsell.com
Open Graph description is not detected on the main page of Footsell. 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: