6.3 sec in total
187 ms
5.8 sec
292 ms
Welcome to fitwear.co.nz homepage info - get ready to check Fitwear best content right away, or after learning these important things about fitwear.co.nz
Visit fitwear.co.nzWe analyzed Fitwear.co.nz page load time and found that the first response time was 187 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster. This domain responded with an error, which can significantly jeopardize Fitwear.co.nz rating and web reputation
fitwear.co.nz performance score
name
value
score
weighting
Value2.9 s
51/100
10%
Value6.7 s
7/100
25%
Value5.1 s
62/100
10%
Value480 ms
60/100
30%
Value1.324
0/100
15%
Value12.3 s
15/100
10%
187 ms
497 ms
28 ms
16 ms
1402 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fitwear.co.nz, 11% (15 requests) were made to Static.xx.fbcdn.net and 7% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.9 MB (23%)
8.1 MB
6.3 MB
In fact, the total size of Fitwear.co.nz main page is 8.1 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 6.2 MB which makes up the majority of the site volume.
Potential reduce by 63.3 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 12.4 kB, which is 15% 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 63.3 kB or 79% of the original size.
Potential reduce by 439.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. Fitwear images are well optimized though.
Potential reduce by 1.1 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 1.1 MB or 69% of the original size.
Potential reduce by 276.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. Fitwear.co.nz needs all CSS files to be minified and compressed as it can save up to 276.8 kB or 84% of the original size.
Number of requests can be reduced by 67 (58%)
116
49
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fitwear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.fitwear.net
187 ms
2792330287.js
497 ms
timber.scss.css
28 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
16 ms
load.sumome.com
1402 ms
jquery.min.js
30 ms
css
23 ms
font-awesome.min.css
6 ms
modernizr.min.js
16 ms
jquery.flexslider.min.js
20 ms
shop.js
17 ms
ajaxify.scss.css
19 ms
handlebars.min.js
26 ms
ajaxify.js
22 ms
currencies.js
22 ms
event
55 ms
shopify_stats.js
34 ms
trekkie.storefront.min.js
99 ms
shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js
33 ms
main.js
306 ms
logo.png
19 ms
slide_1.jpg
72 ms
best_sellers_large_3e1674e9-5006-4878-ae36-156668bf8900_large.png
67 ms
new_releases_large_9d851133-f318-4416-b0a3-151e5730f2a0_large.png
66 ms
sets_large.jpg
58 ms
womens_large_3268e80e-a577-4eff-a19e-94aab9b1063b_large.jpg
65 ms
mens_large_dd58aafc-f6e7-4d06-b998-d476c4c0b0d4_large.jpg
66 ms
footer_payment.jpg
67 ms
5_large.png
208 ms
best_sellers_large_3e1674e9-5006-4878-ae36-156668bf8900_large.png
80 ms
1_large.png
190 ms
3_large.png
206 ms
7_large.png
208 ms
2016SSBANNER.jpg
187 ms
22OFFBANNER.jpg
82 ms
banner1.jpg
186 ms
AUSDAY.jpg
205 ms
AZTECBANNER.jpg
334 ms
BANNER.gif
324 ms
FWBANNER.jpg
595 ms
banner1_6464c373-bdee-4973-8f7a-f0b91e47f33c.png
340 ms
VALENTINESBANNER.png
555 ms
Banner1_d59de76f-a5df-464c-8f23-f5bbd44be23d.jpg
323 ms
LEGGINGSRELEASE_BANNER.jpg
325 ms
LEGGINGS_LIVENOW_BANNER.jpg
337 ms
Futura-Book.woff
177 ms
record.gif
289 ms
identify
292 ms
analytics.js
88 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
57 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
58 ms
fontawesome-webfont.woff
40 ms
icons.woff
54 ms
sdk.js
396 ms
collect
93 ms
collect
131 ms
page
163 ms
update.html
90 ms
config
55 ms
blips
149 ms
widget_v2.134.js
37 ms
159 ms
xd_arbiter.php
217 ms
xd_arbiter.php
2356 ms
sca-qv-scripts-noconfig.js
69 ms
shopify_rolling_bootstrap.js
144 ms
pixel.js
268 ms
collect
47 ms
286 ms
roundtrip.js
13 ms
jquery.min.js
32 ms
json2.min.js
12 ms
cart.js
137 ms
index
156 ms
page.php
201 ms
JY6YMFMUXFHEJJYPHTI4MB.js
305 ms
pub_8a1f4d90c55244073645.js
90 ms
LUdypCgtRlc.css
2115 ms
Hy2B8ciSPhU.css
2192 ms
q68gy-v_YMF.js
2393 ms
YvxwM8R7ol8.js
2466 ms
ihptErjAmMX.js
2417 ms
1BQnIVjTFoC.js
2483 ms
6PDLJFN-l6_.js
2490 ms
cUsKAwzqrQw.js
2495 ms
chatbox.css
30 ms
css
1985 ms
font-awesome.min.css
1982 ms
chatbox.css
119 ms
css
1983 ms
service.js
1953 ms
avatar_simple_visitor.png
802 ms
fbevents.hashing.js
106 ms
out
26 ms
26 ms
30 ms
out
18 ms
out
21 ms
out
21 ms
out
25 ms
out
24 ms
out
24 ms
out
28 ms
out
27 ms
79 ms
fontawesome-webfont.woff
51 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
100 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
100 ms
aL63HcygAAVYuCCsAAA==
14 ms
sme-popup.css
49 ms
u.php
106 ms
adsct
138 ms
pixel
105 ms
96 ms
load
256 ms
sync
37 ms
css
37 ms
47 ms
64 ms
377928.gif
26 ms
sd
15 ms
tap.php
21 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
5 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
16 ms
in
14 ms
12803116_1068272786570911_599983061484568235_n.jpg
353 ms
11800347_949799661751558_4724970745302401547_n.jpg
422 ms
947348_1105911352794975_2509005526188636431_n.jpg
492 ms
12715305_802037543257977_5451157980575249713_n.jpg
554 ms
11065897_10205413330746440_2699629309935560727_n.jpg
555 ms
12669647_1071019696281709_1915172876899017755_n.jpg
556 ms
12801403_1066357273422362_8856786082923243182_n.jpg
556 ms
12654490_216918498662319_3392760313653592913_n.jpg
555 ms
12509115_190999364587549_2553386980301473445_n.jpg
559 ms
12688081_470466079826371_5967537280220452068_n.jpg
621 ms
wL6VQj7Ab77.png
104 ms
s7jcwEQH7Sx.png
105 ms
6GqoI2ZyIrf.png
70 ms
R9a_DtVRZgv.js
69 ms
cUDgRFxaoIk.js
69 ms
0JBr1QHp8Gi.js
70 ms
kDOzhTr2W91.js
72 ms
fitwear.co.nz 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-hidden="true"] elements contain focusable descendents
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
[id] attributes on active, focusable elements are not unique
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
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.
fitwear.co.nz 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
Missing source maps for large first-party JavaScript
fitwear.co.nz 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
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 Fitwear.co.nz 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 Fitwear.co.nz 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.
fitwear.co.nz
Open Graph description is not detected on the main page of Fitwear. 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: