4.6 sec in total
376 ms
3.8 sec
475 ms
Welcome to geox.com homepage info - get ready to check Geox best content for Italy right away, or after learning these important things about geox.com
Discover the collection of apparel, shoes and accessories on the official Geox site. Safe payment and free return!
Visit geox.comWe analyzed Geox.com page load time and found that the first response time was 376 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
geox.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value9.2 s
1/100
25%
Value17.3 s
0/100
10%
Value12,140 ms
0/100
30%
Value0.669
8/100
15%
Value29.8 s
0/100
10%
376 ms
476 ms
284 ms
202 ms
304 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 14% of them (20 requests) were addressed to the original Geox.com, 27% (40 requests) were made to Demandware.edgesuite.net and 5% (8 requests) were made to Segments.adaptv.advertising.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Demandware.edgesuite.net.
Page size can be reduced by 4.5 MB (51%)
8.8 MB
4.3 MB
In fact, the total size of Geox.com main page is 8.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. 80% 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. Javascripts take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 233.8 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 32.1 kB, which is 11% 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 233.8 kB or 79% of the original size.
Potential reduce by 73.4 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. Geox images are well optimized though.
Potential reduce by 2.8 MB
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 2.8 MB or 70% of the original size.
Potential reduce by 1.4 MB
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. Geox.com needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 74% of the original size.
Number of requests can be reduced by 77 (61%)
126
49
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geox. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
start
376 ms
start
476 ms
style.css
284 ms
fonts.css
202 ms
jquery-ui-1.11.0.css
304 ms
main-libs.min.js
583 ms
dwac-14.8.js
205 ms
geox_fonts.css
184 ms
js
43 ms
app_core.js
689 ms
addthis_widget.js
9 ms
app_geox.js
387 ms
dwanalytics.js
200 ms
gretel.min.js
10 ms
style-blessed1.css
476 ms
logo-icon-eng.jpg
388 ms
Spring-Issue_en.jpg
476 ms
nebula_woman_en.jpg
386 ms
nebula_man_en.jpg
474 ms
ultra-light_girl_en.jpg
473 ms
ultra-light_boy_en.jpg
386 ms
ambhibiox_en_2.jpg
475 ms
google.png
473 ms
linkedin.png
472 ms
microsoft.png
566 ms
facebook.png
566 ms
github.jpeg
567 ms
CUSTOMER_CARE.jpg
566 ms
1.jpg
841 ms
2.jpg
824 ms
right-arrow.png
669 ms
1.jpg
937 ms
2_en.jpg
669 ms
3_en.jpg
654 ms
1.jpg
948 ms
2.jpg
944 ms
3.jpg
948 ms
2.jpg
1146 ms
Nebula_en.jpg
944 ms
U52D7B01185_C1000_home.png
1292 ms
nebulabreathing2.jpg
1067 ms
breathable.png
1066 ms
lightness.png
1064 ms
1.jpg
1234 ms
D4258A000NF_C8182_home.png
1505 ms
D620SA00085_C9999_home.png
1458 ms
D62N1A000HH_C9999_home.png
1487 ms
D621BA000KY_C8124_home.png
1689 ms
gtm.js
376 ms
HelveticaNeueLTW1G-UltLt.svg
343 ms
HelveticaLight.svg
522 ms
HelveticaNeueRegular.svg
429 ms
HelveticaNeue.svg
428 ms
HelveticaNeueLTW1G-It.svg
609 ms
Tlqjxdu6ZZ0
416 ms
right-arrow.png
1285 ms
QDtxXOWi9-o
426 ms
HelveticaNeueLTW1G-Bd.svg
581 ms
geox-icons.woff
267 ms
300lo.json
191 ms
sh.7c7179124ea24ac6ba46caac.html
99 ms
roundtrip.js
56 ms
analytics.js
115 ms
tag.js
182 ms
4505.js
46 ms
1875
277 ms
hotjar-20340.js
177 ms
prum.min.js
40 ms
assist.js
106 ms
MasterTMS.min.js
101 ms
code.js
267 ms
www-embed-player-vflZsBgOl.css
188 ms
www-embed-player.js
332 ms
base.js
495 ms
HelveticaNeueLTW1G-UltLt.woff
159 ms
tag.js
149 ms
sgtracker.js
126 ms
139 ms
s
246 ms
tags
118 ms
linkid.js
47 ms
ec.js
104 ms
101 ms
104 ms
104 ms
105 ms
104 ms
185 ms
184 ms
u
249 ms
HelveticaNeueRegular.woff
190 ms
HelveticaNeue.woff
242 ms
HelveticaLight.woff
189 ms
capture-apps-4.9.1.js
86 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
200 ms
zylgazhm.js
181 ms
JWBM4J77ZFHH7AUHWAHUAM.js
424 ms
HelveticaNeueLTW1G-It.woff
331 ms
HelveticaNeueLTW1G-Bd.woff
329 ms
.jsonp
143 ms
collect
86 ms
collect
197 ms
yieldify_1449674132.js
118 ms
1875
169 ms
1875
303 ms
skimtag.geox.com.js
72 ms
collect
288 ms
collect
70 ms
iframeStorage.html
276 ms
134E4E7D-289E-48FB-BACC-5E3DC75CB035
85 ms
79 ms
78 ms
mTag.js
149 ms
skimtag
12 ms
ga-audiences
151 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
64 ms
ad_status.js
109 ms
__Analytics-Tracking
121 ms
pixel
43 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
93 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
116 ms
appsmanagerinit
253 ms
iframeStorage.js
38 ms
pixel
50 ms
pixel
47 ms
45 ms
44 ms
pixel
32 ms
out
22 ms
tr
39 ms
22 ms
19 ms
out
22 ms
out
22 ms
out
25 ms
out
25 ms
out
26 ms
41 ms
36 ms
pixel
47 ms
sync
19 ms
tap.php
27 ms
377928.gif
11 ms
11 ms
in
7 ms
sd
29 ms
tap.php
291 ms
nr-476.min.js
19 ms
geox.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
geox.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
Issues were logged in the Issues panel in Chrome Devtools
geox.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geox.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 Geox.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.
geox.com
Open Graph data is detected on the main page of Geox. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: