Tools & Wizards About Us
gzox.com screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

gzox.com

ガラス系コーティング【G'ZOX】｜プレミアムカーコーティングブランド

Page Load Speed

5.3 sec in total

First Response

712 ms

Resources Loaded

4.4 sec

Page Rendered

195 ms

gzox.com screenshot

About Website

Welcome to gzox.com homepage info - get ready to check G ZOX best content for Japan right away, or after learning these important things about gzox.com

ガラス系コーティング剤G'ZOX(ジーゾックス)公式サイト。輝きが生む至上の悦び。自動車のプロも納得のガラス系コーティング・ボディコーティングで貴方の愛車に透き通る輝きを。コーティング剤「リアルガラスコート」「ガードグレイズ」「ハイモース コート」の公式サイトです。

Visit gzox.com

Key Findings

We analyzed Gzox.com page load time and found that the first response time was 712 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

gzox.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.515

15/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

gzox.com

712 ms

www.gzox.com

1144 ms

beautiful.css

493 ms

rollover.js

331 ms

flash_config.js

334 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 52% of them (39 requests) were addressed to the original Gzox.com, 4% (3 requests) were made to S.ytimg.com and 4% (3 requests) were made to Js.fout.jp. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Gzox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 466.2 kB (47%)

Content Size

995.1 kB

After Optimization

528.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gzox.com main page is 995.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 357.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 21.6 kB

  • Original 30.0 kB
  • After minification 29.1 kB
  • After compression 8.4 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 21.6 kB or 72% of the original size.

Image Optimization

-9%

Potential reduce by 31.2 kB

  • Original 357.0 kB
  • After minification 325.8 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. G ZOX images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 182.5 kB

  • Original 330.3 kB
  • After minification 329.0 kB
  • After compression 147.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 182.5 kB or 55% of the original size.

CSS Optimization

-83%

Potential reduce by 230.9 kB

  • Original 277.8 kB
  • After minification 269.4 kB
  • After compression 46.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. Gzox.com needs all CSS files to be minified and compressed as it can save up to 230.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (45%)

Requests Now

69

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G ZOX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

gzox.com

gzox.com

712 ms

www.gzox.com

www.gzox.com

1144 ms

beautiful.css

beautiful.css

493 ms

rollover.js

rollover.js

331 ms

flash_config.js

flash_config.js

334 ms

jquery-1.2.6.pack.js

jquery-1.2.6.pack.js

716 ms

multihero.js

multihero.js

369 ms

widgets.js

widgets.js

5 ms

ga.js

ga.js

15 ms

bg_wrapper_index.jpg

bg_wrapper_index.jpg

212 ms

logo.gif

logo.gif

211 ms

lang_en_off.gif

lang_en_off.gif

174 ms

lang_cn_off.gif

lang_cn_off.gif

174 ms

btn_info_off.jpg

btn_info_off.jpg

211 ms

btn_tec_off.jpg

btn_tec_off.jpg

174 ms

btn_partner_off.jpg

btn_partner_off.jpg

336 ms

btn_store_off.jpg

btn_store_off.jpg

336 ms

btn_report_off.jpg

btn_report_off.jpg

336 ms

btn_mainte_off.jpg

btn_mainte_off.jpg

456 ms

btn_qa_off.jpg

btn_qa_off.jpg

456 ms

btn_media_off.jpg

btn_media_off.jpg

457 ms

main_01.jpg

main_01.jpg

830 ms

main_02.jpg

main_02.jpg

826 ms

ttl_shopsrech.jpg

ttl_shopsrech.jpg

664 ms

ttl_serch_01.gif

ttl_serch_01.gif

566 ms

ttl_serch_02.gif

ttl_serch_02.gif

566 ms

ttl_serch_03.gif

ttl_serch_03.gif

733 ms

ttl_serch_04.gif

ttl_serch_04.gif

716 ms

bnr_pp.jpg

bnr_pp.jpg

719 ms

ttl_movie.jpg

ttl_movie.jpg

830 ms

ttl_news.jpg

ttl_news.jpg

895 ms

ttl_social.jpg

ttl_social.jpg

899 ms

bnr_blog.jpg

bnr_blog.jpg

916 ms

bnr_facebook.jpg

bnr_facebook.jpg

988 ms

bnr_twitter.jpg

bnr_twitter.jpg

992 ms

bnr_youtube.jpg

bnr_youtube.jpg

995 ms

footer.jpg

footer.jpg

1072 ms

all.js

all.js

200 ms

bg_navi.jpg

bg_navi.jpg

1074 ms

__utm.gif

__utm.gif

14 ms

bg_contents.jpg

bg_contents.jpg

1034 ms

collect

collect

88 ms

bg_serch.jpg

bg_serch.jpg

1047 ms

bg_footer.jpg

bg_footer.jpg

1054 ms

tag.js

tag.js

12 ms

gtm.js

gtm.js

60 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

39 ms

4iAdCZZYvyo

4iAdCZZYvyo

144 ms

like.php

like.php

209 ms

tag

tag

30 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

38 ms

199 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

21 ms

www-embed-player.js

www-embed-player.js

40 ms

base.js

base.js

81 ms

xd_arbiter.php

xd_arbiter.php

196 ms

xd_arbiter.php

xd_arbiter.php

320 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

365 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

405 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

74 ms

ad_status.js

ad_status.js

70 ms

jot

jot

146 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

51 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

54 ms

ya.js

ya.js

357 ms

segmentation.js

segmentation.js

14 ms

conversion_async.js

conversion_async.js

31 ms

beacon.html

beacon.html

8 ms

cnt

cnt

388 ms

conversion.js

conversion.js

392 ms

38 ms

18 ms

pb.js

pb.js

552 ms

317 ms

351 ms

Accessibility Review

gzox.com accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

gzox.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gzox.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gzox.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Gzox.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

gzox.com

Open Graph description is not detected on the main page of G ZOX. 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: