Tools & Wizards About Us
defend.co.jp screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    45% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

defend.co.jp

GT-R専門店 GARAGE DEFEND

Page Load Speed

62.9 sec in total

First Response

8.5 sec

Resources Loaded

54.3 sec

Page Rendered

135 ms

defend.co.jp screenshot

About Website

Welcome to defend.co.jp homepage info - get ready to check DEFEND best content for Japan right away, or after learning these important things about defend.co.jp

GT-R専門店 ガレージ ディフェンド スカイラインGT-R R32,R33,R34,R35 その他GTスポーツカーのことならお任せください

Visit defend.co.jp

Key Findings

We analyzed Defend.co.jp page load time and found that the first response time was 8.5 sec and then it took 54.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

defend.co.jp performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,460 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

defend.co.jp

8456 ms

rollover.js

1351 ms

rollover2.js

4514 ms

heightLine.js

5807 ms

jsapi

41 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 58% of them (42 requests) were addressed to the original Defend.co.jp, 14% (10 requests) were made to Static.xx.fbcdn.net and 8% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Defend.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 383.2 kB (66%)

Content Size

578.0 kB

After Optimization

194.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Defend.co.jp main page is 578.0 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. 35% of websites need less resources to load. CSS take 253.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 9.7 kB

  • Original 13.3 kB
  • After minification 12.2 kB
  • After compression 3.6 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 9.7 kB or 73% of the original size.

Image Optimization

-25%

Potential reduce by 18.7 kB

  • Original 74.9 kB
  • After minification 56.2 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. Obviously, DEFEND needs image optimization as it can save up to 18.7 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 145.2 kB

  • Original 236.5 kB
  • After minification 231.4 kB
  • After compression 91.3 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 145.2 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 209.6 kB

  • Original 253.3 kB
  • After minification 251.2 kB
  • After compression 43.7 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. Defend.co.jp needs all CSS files to be minified and compressed as it can save up to 209.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (34%)

Requests Now

70

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

defend.co.jp

defend.co.jp

8456 ms

rollover.js

rollover.js

1351 ms

rollover2.js

rollover2.js

4514 ms

heightLine.js

heightLine.js

5807 ms

jsapi

jsapi

41 ms

blog.js

blog.js

10402 ms

photoshuffler.js

photoshuffler.js

7973 ms

reset.css

reset.css

5274 ms

top.css

top.css

11038 ms

bace.css

bace.css

5474 ms

16 ms

default+en.css

default+en.css

2 ms

default+en.I.js

default+en.I.js

3 ms

ga.js

ga.js

29 ms

bg_head_under.gif

bg_head_under.gif

1748 ms

gvHa74BK4BE

gvHa74BK4BE

80 ms

profile.cgi

profile.cgi

19958 ms

bg_head.gif

bg_head.gif

10009 ms

l_service.png

l_service.png

1203 ms

l_shopguide.png

l_shopguide.png

3005 ms

l_blog.png

l_blog.png

5005 ms

l_gallery.png

l_gallery.png

3006 ms

l_contact.png

l_contact.png

6557 ms

link_racing.gif

link_racing.gif

8187 ms

t_shopinfo.png

t_shopinfo.png

4190 ms

l_defend.png

l_defend.png

10004 ms

l_icon_contact.png

l_icon_contact.png

5194 ms

l_telfax.png

l_telfax.png

5896 ms

l_icon_add.png

l_icon_add.png

7002 ms

l_icon_time.png

l_icon_time.png

7849 ms

l_icon_holiday.png

l_icon_holiday.png

7186 ms

defend_logo.png

defend_logo.png

19955 ms

top_img01.jpg

top_img01.jpg

19958 ms

whatnew_base.png

whatnew_base.png

14084 ms

blog_base.gif

blog_base.gif

19958 ms

t_b_blog.gif

t_b_blog.gif

12872 ms

youtube_base.png

youtube_base.png

19958 ms

blog_b_32.gif

blog_b_32.gif

15001 ms

blog_b_33.gif

blog_b_33.gif

16999 ms

blog_b_34.gif

blog_b_34.gif

17203 ms

blog_b_35.gif

blog_b_35.gif

19957 ms

__utm.gif

__utm.gif

17 ms

likebox.php

likebox.php

88 ms

www-embed-player-vfl-z2BtK.css

www-embed-player-vfl-z2BtK.css

88 ms

www-embed-player.js

www-embed-player.js

108 ms

base.js

base.js

169 ms

V89xIM8XrVh.css

V89xIM8XrVh.css

97 ms

mKIPuHvlbBA.css

mKIPuHvlbBA.css

201 ms

XCdv7aD40Gm.js

XCdv7aD40Gm.js

208 ms

lnwXDK64af8.js

lnwXDK64af8.js

285 ms

mn6tHWuLI-Y.js

mn6tHWuLI-Y.js

236 ms

x8BMxYCqTb9.js

x8BMxYCqTb9.js

237 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

41 ms

ad_status.js

ad_status.js

90 ms

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff

80 ms

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff

80 ms

12509291_970238896398012_8033442116634215206_n.jpg

12509291_970238896398012_8033442116634215206_n.jpg

79 ms

182590_306229109465664_1407813084_n.jpg

182590_306229109465664_1407813084_n.jpg

94 ms

12321260_856784237764250_1621392492403931187_n.jpg

12321260_856784237764250_1621392492403931187_n.jpg

112 ms

12400465_504249609752019_3223507453199336172_n.jpg

12400465_504249609752019_3223507453199336172_n.jpg

129 ms

10547455_348660161951380_1429725044250024133_n.jpg

10547455_348660161951380_1429725044250024133_n.jpg

137 ms

1623716_405102722958410_871612216_n.jpg

1623716_405102722958410_871612216_n.jpg

130 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

27 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

26 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

21 ms

50Trs1RKgUY.js

50Trs1RKgUY.js

19 ms

f_tradein.gif

f_tradein.gif

19755 ms

r_back.png

r_back.png

19290 ms

tel.png

tel.png

19766 ms

r_b_max.gif

r_b_max.gif

17728 ms

t_ameba.png

t_ameba.png

20061 ms

r_blog.gif

r_blog.gif

20415 ms

r_b_blogold.gif

r_b_blogold.gif

18998 ms

Accessibility Review

defend.co.jp accessibility score

59

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

defend.co.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

defend.co.jp SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Defend.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Defend.co.jp 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.

Social Sharing Optimization

defend.co.jp

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