Tools & Wizards About Us
gizmodo.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

gizmodo.jp

ギズモード・ジャパン | 日本最大級のガジェット＆テクノロジーサイト

Page Load Speed

6.4 sec in total

First Response

17 ms

Resources Loaded

5.8 sec

Page Rendered

549 ms

gizmodo.jp screenshot

About Website

Click here to check amazing Gizmodo content for Japan. Otherwise, check out these important facts you probably never knew about gizmodo.jp

GIZMODO JAPAN（ギズモード・ジャパン）は最新のスマートフォンなどのデジタルデバイス情報や最新のガジェット情報から、テクノロジー、サイエンス、ビジネス、エンターテイメントの情報まで、刺激的で他とは違う情報をお届けします。

Visit gizmodo.jp

Key Findings

We analyzed Gizmodo.jp page load time and found that the first response time was 17 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

gizmodo.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value23.2 s

0/100

25%

SI (Speed Index)

Value27.2 s

0/100

10%

TBT (Total Blocking Time)

Value5,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value36.9 s

0/100

10%

Network Requests Diagram

gizmodo.jp

17 ms

gizmodo.jp

194 ms

www.gizmodo.jp

42 ms

font-awesome.min.css

9 ms

main.css

22 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 22% of them (27 requests) were addressed to the original Gizmodo.jp, 14% (17 requests) were made to Media.loom-app.com and 4% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Gizmodo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.6 kB (10%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gizmodo.jp main page is 1.6 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. 70% of websites need less resources to load. Javascripts take 969.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 116.6 kB

  • Original 147.4 kB
  • After minification 147.3 kB
  • After compression 30.9 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 116.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 387.9 kB
  • After minification 387.9 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. Gizmodo images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 26.0 kB

  • Original 969.1 kB
  • After minification 969.1 kB
  • After compression 943.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-26%

Potential reduce by 14.0 kB

  • Original 54.3 kB
  • After minification 54.3 kB
  • After compression 40.3 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. Gizmodo.jp needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (70%)

Requests Now

111

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gizmodo.jp

gizmodo.jp

17 ms

gizmodo.jp

gizmodo.jp

194 ms

www.gizmodo.jp

www.gizmodo.jp

42 ms

font-awesome.min.css

font-awesome.min.css

9 ms

main.css

main.css

22 ms

css

css

77 ms

css

css

94 ms

jquery.min.js

jquery.min.js

49 ms

cx.js

cx.js

81 ms

bookmark_button.js

bookmark_button.js

70 ms

loader.min.js

loader.min.js

674 ms

cx-action.js

cx-action.js

73 ms

media-connect.js

media-connect.js

73 ms

lazysizes.min.js

lazysizes.min.js

50 ms

gpt.js

gpt.js

416 ms

swiper.jquery.min.js

swiper.jquery.min.js

47 ms

slick.min.js

slick.min.js

62 ms

main.js

main.js

62 ms

taxonomies.js

taxonomies.js

60 ms

tag_cloud.js

tag_cloud.js

59 ms

gtm.js

gtm.js

402 ms

12384.js

12384.js

809 ms

apstag.js

apstag.js

379 ms

seg.js

seg.js

1404 ms

sns_icon_x.svg

sns_icon_x.svg

371 ms

240426_scientific-sugoi-matome.jpg

240426_scientific-sugoi-matome.jpg

2801 ms

increment-pv

increment-pv

1719 ms

taxonomies

taxonomies

5000 ms

tag-cloud

tag-cloud

737 ms

sns_icon_tiktok.svg

sns_icon_tiktok.svg

528 ms

sns_icon_youtube.svg

sns_icon_youtube.svg

523 ms

sns_icon_discord.svg

sns_icon_discord.svg

525 ms

icon_search.svg

icon_search.svg

524 ms

icon_pv.svg

icon_pv.svg

1117 ms

common_icon_arrow_slide.svg

common_icon_arrow_slide.svg

946 ms

common_icon_arrow_more.svg

common_icon_arrow_more.svg

1115 ms

sns_icon_x_fff.svg

sns_icon_x_fff.svg

944 ms

sns_icon_tiktok_fff.svg

sns_icon_tiktok_fff.svg

1113 ms

sns_icon_youtube_fff.svg

sns_icon_youtube_fff.svg

1451 ms

sns_icon_discord_fff.svg

sns_icon_discord_fff.svg

1503 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

260 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

261 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

510 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

519 ms

m8JXjfVPf62XiF7kO-i9YLNlbg.ttf

m8JXjfVPf62XiF7kO-i9YLNlbg.ttf

625 ms

pubads_impl.js

pubads_impl.js

71 ms

A7309263_1227.jpg

A7309263_1227.jpg

3668 ms

240423_pixelanimations_top2.jpg

240423_pixelanimations_top2.jpg

3170 ms

240322_005-1.jpg

240322_005-1.jpg

1204 ms

wirelessheadphone_main.jpg

wirelessheadphone_main.jpg

2236 ms

202405_thum_iphone.png

202405_thum_iphone.png

2232 ms

2040425-bag-hanger-clipa-01.jpg

2040425-bag-hanger-clipa-01.jpg

3002 ms

js

js

319 ms

js

js

508 ms

analytics.js

analytics.js

681 ms

destination

destination

497 ms

163 ms

destination

destination

491 ms

uwt.js

uwt.js

764 ms

yads.js

yads.js

1392 ms

gizmodo.js

gizmodo.js

1556 ms

quant.js

quant.js

695 ms

ff99f90aa76b56e4_2524.js

ff99f90aa76b56e4_2524.js

1411 ms

obtp.js

obtp.js

767 ms

cx.cce.js

cx.cce.js

153 ms

sdk.js

sdk.js

634 ms

s_retargeting.js

s_retargeting.js

1217 ms

chartbeat_mab.js

chartbeat_mab.js

673 ms

fbevents.js

fbevents.js

688 ms

tfa.js

tfa.js

770 ms

sdk.js

sdk.js

675 ms

main.js

main.js

837 ms

tentacle.js

tentacle.js

736 ms

iui3

iui3

249 ms

sdk.js

sdk.js

136 ms

im-uid.js

im-uid.js

248 ms

collect

collect

99 ms

collect

collect

228 ms

publisher:getClientId

publisher:getClientId

259 ms

insight.js

insight.js

178 ms

json

json

114 ms

adsct

adsct

237 ms

adsct

adsct

200 ms

adsct

adsct

158 ms

adsct

adsct

177 ms

get

get

283 ms

202402_thum.png

202402_thum.png

891 ms

240426_audicharginghub_top-1.jpg

240426_audicharginghub_top-1.jpg

898 ms

20240414-sonicare-gentleplus-01.jpg

20240414-sonicare-gentleplus-01.jpg

895 ms

DSC_7635.jpg

DSC_7635.jpg

899 ms

gizmodo_midjourney_a_boy_wearing_wireless_transparent_headphone_b0f29553-cbc1-4171-a9ec-9fdd54fc4880-1.jpg

gizmodo_midjourney_a_boy_wearing_wireless_transparent_headphone_b0f29553-cbc1-4171-a9ec-9fdd54fc4880-1.jpg

905 ms

collect

collect

19 ms

collect

collect

15 ms

ga-audiences

ga-audiences

77 ms

129

129

358 ms

cds-pips.js

cds-pips.js

5 ms

eid.es5.js

eid.es5.js

8 ms

pips.taboola.com

pips.taboola.com

54 ms

collect

collect

27 ms

collect

collect

7 ms

collect

collect

14 ms

ga-audiences

ga-audiences

24 ms

collect

collect

702 ms

tracking.min.js

tracking.min.js

81 ms

td_js_sdk_171.js

td_js_sdk_171.js

169 ms

discoverylogs

discoverylogs

673 ms

recommend

recommend

775 ms

popin_discovery5-min.js

popin_discovery5-min.js

657 ms

discoverylogs

discoverylogs

683 ms

184

184

276 ms

220208ApplePencilholder-01.jpg

220208ApplePencilholder-01.jpg

973 ms

top_light-06.jpg

top_light-06.jpg

1312 ms

popin_send_cookie_set_fail.js

popin_send_cookie_set_fail.js

167 ms

discoverylogs

discoverylogs

162 ms

log.gif

log.gif

695 ms

chartbeat.js

chartbeat.js

51 ms

rep

rep

204 ms

mab

mab

22 ms

ping

ping

19 ms

240419xrealhub2.jpg

240419xrealhub2.jpg

10 ms

240317_Ts_3023_1st_144ppi.jpg

240317_Ts_3023_1st_144ppi.jpg

954 ms

2024-05-01sak00.jpg

2024-05-01sak00.jpg

1322 ms

Accessibility Review

gizmodo.jp accessibility score

88

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

<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

Best Practices

gizmodo.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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

gizmodo.jp SEO score

84

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

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gizmodo.jp 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 Gizmodo.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

gizmodo.jp

Open Graph data is detected on the main page of Gizmodo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: