7.1 sec in total
1.2 sec
5.7 sec
205 ms
Click here to check amazing Zgear content for Singapore. Otherwise, check out these important facts you probably never knew about zgear.us
Visit zgear.usWe analyzed Zgear.us page load time and found that the first response time was 1.2 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
zgear.us performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value3.7 s
57/100
25%
Value4.6 s
71/100
10%
Value110 ms
98/100
30%
Value0.032
100/100
15%
Value4.0 s
88/100
10%
1195 ms
1166 ms
1382 ms
463 ms
457 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 70% of them (37 requests) were addressed to the original Zgear.us, 19% (10 requests) were made to Divecms.wowtv.com and 8% (4 requests) were made to Code.createjs.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Divecms.wowtv.com.
Page size can be reduced by 166.6 kB (14%)
1.2 MB
998.1 kB
In fact, the total size of Zgear.us main page is 1.2 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. 35% of websites need less resources to load. Images take 980.1 kB which makes up the majority of the site volume.
Potential reduce by 23.5 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 7.6 kB, which is 26% 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 23.5 kB or 82% of the original size.
Potential reduce by 30.6 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. Zgear images are well optimized though.
Potential reduce by 77.7 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 77.7 kB or 68% of the original size.
Potential reduce by 34.9 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. Zgear.us needs all CSS files to be minified and compressed as it can save up to 34.9 kB or 84% of the original size.
Number of requests can be reduced by 15 (29%)
51
36
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zgear. 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 4 to 1 for CSS and as a result speed up the page load time.
zgear.us
1195 ms
styles.css
1166 ms
jquery-1.3.2.min.js
1382 ms
jqueryslidemenu.css
463 ms
jqueryslidemenu.js
457 ms
scripts.js
450 ms
SaveCheck.js
686 ms
css
27 ms
WebResource.axd
1371 ms
ScriptResource.axd
2151 ms
ScriptResource.axd
1225 ms
easeljs-0.7.0.min.js
8 ms
tweenjs-0.5.0.min.js
5 ms
movieclip-0.7.0.min.js
5 ms
preloadjs-0.4.0.min.js
7 ms
banner_flash.js
481 ms
loopedslider.js
740 ms
3_6174331829.jpg
1435 ms
logo.gif
275 ms
tdcc.png
270 ms
icoSearch.gif
264 ms
icoCart.gif
262 ms
leftlogo_wowtv.png
285 ms
leftlogo_dive.png
492 ms
simdilogo.png
521 ms
leftlogo_ori.png
508 ms
leftlogo_mygem.png
521 ms
leftlogo_clubfeida.png
522 ms
leftlogo_bella.png
711 ms
btnShopNow.gif
746 ms
rightlogo_tdc.png
758 ms
rightlogo_tdcclub.png
816 ms
rightlogo_tdccdive.png
759 ms
rightlogo_tdccestore.png
934 ms
rightlogo_tdcg.png
998 ms
imgPaypal.gif
990 ms
1_7152959785.jpg
816 ms
1_1013426890.jpg
2993 ms
1_9115027513.jpg
816 ms
Category22151326615.jpg
816 ms
Category8213959252.jpg
1702 ms
Category9173926659.jpg
1008 ms
Category2212353433.jpg
1031 ms
Category2215156349.jpg
1500 ms
Category2215556721.jpg
1892 ms
bgSearch.gif
231 ms
bgMenu.gif
245 ms
bgMenuSeparator.gif
238 ms
bgHome.gif
1251 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
31 ms
styles.css
411 ms
bgHomeBanner.gif
412 ms
divestyle_01.jpg
724 ms
zgear.us 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.
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
<frame> or <iframe> elements do not have a title
zgear.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
zgear.us SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zgear.us 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Zgear.us 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.
zgear.us
Open Graph description is not detected on the main page of Zgear. 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: