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

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

Page load speed analysis

  • 54/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    304 ms

  • Resources loaded

    3.1 sec

  • Page rendered

    838 ms

  • Total page load time

    4.3 sec

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

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

Page optimization

  • HTML 116.9 kB
    Images 6.8 MB
    Javascripts 651.5 kB
    CSS 108.8 kB

    In fact, the total size of main page is 7.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. 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.8 MB which makes up the majority of the site volume.

    • Original 116.9 kB
    • After minification 88.3 kB
    • After compression 19.9 kB

    HTML optimization

    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 28.6 kB, which is 24% 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 97.0 kB or 83% of the original size.

    • Original 6.8 MB
    • After optimization 6.3 MB

    Image optimization

    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.

    • Original 651.5 kB
    • After minification 640.5 kB
    • After compression 197.9 kB

    JavaScript optimization

    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 453.6 kB or 70% of the original size.

    • Original 108.8 kB
    • After minification 90.5 kB
    • After compression 17.5 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 91.3 kB or 84% of the original size.

Network requests diagram

  • ua.js
  • style.css
  • style.css
  • css
  • jquery.min.js
  • topsy.js
  • bookmark_button.js
  • plusone.js
  • jquery.lazyload.min.js
  • ipad_delswitch.js
  • headline.js
  • headbar_fixed.js
  • show_ads.js
  • brand
  • pjs.js
  • aps-base.min.js
  • 58690X1363955.skimlinks.js
  • HT201285
  • dc.js
  • cb=gapi.loaded_0
  • bg.jpg
  • ir
  • 160226ktddnobu.jpg
  • ir
  • ir
  • ir
  • ir
  • 160226sirionmac-thumb-126x126-140716.jpg
  • 160226_city_01.jpg
  • 160227cloverfield2.jpg
  • 160226talentedskier.jpg
  • ic_movie.png
  • 20160216nikon1_Rs.JPG
  • 20160228nikon_digital_oshirase.jpg
  • 160226daredevilseason2.jpg
  • 1600218-1600218-DSC_7401-R-R-thumb-640x427-140863.jpg
  • 160229ntaku1-thumb-640x355-140850.jpg
  • 160226CarnegieMellonhack-thumb-640x320-140773.jpg
  • 20160228_googleart01-thumb-700x393-140788.jpg
  • 160229apollo8-thumb-640x480-140868.jpg
  • 160226_shutterstock_302721215.jpg
  • 160227Mercedeshumansback.jpg
  • 160227cloverfield2not.jpg
  • 160226hospitalsecurity-thumb-636x288-140774.jpg
  • 160229applerumors2.jpg
  • 160226_googleselfcar.jpg
  • 160228basedontrue1-thumb-640x360-140815.jpg
  • 160229_leap_day_366.jpg
  • 160209_Applerumors.jpg
  • 20160216writerswanted_mini.jpg
  • snowboardiotmini.jpg
  • 20160225nikon_oshirase_3.jpg
  • apple_fbi.jpg
  • amazarashimini2.jpg
  • mugendai.gif
  • cx.js
  • sdk.js
  • inpage_linkid.js
  • sprite_cat.png
  • iframe
  • sprite4.png
  • google_custom_search_watermark.gif
  • iframe
  • __utm.gif
  • p1.html
  • ca-pub-2605419517314899.js
  • zrt_lookup.html
  • show_ads_impl.js
  • xd_arbiter.php
  • xd_arbiter.php
  • DGr_HuCg-_zePcleoqvEXy3USBnSvpkopQaUR-2r7iU.ttf
  • 31Tjfr7GBJL._SL110_.jpg
  • 51BG3WnhsrL._SL110_.jpg
  • p1.js
  • 5128X8W%2B7GL._SL110_.jpg
  • rep.gif
  • 41iNVNthFeL._SL110_.jpg
  • 41tWs7g1X6L._SL110_.jpg
  • ads
  • osd.js
  • css
  • m_js_controller.js
  • abg.js
  • 160229_chromecast_pd_new.jpg
  • 160229_chromecast_top_new2.jpg
  • js
  • favicon
  • nessie_icon_tiamat_white.png
  • s
  • googlelogo_color_112x36dp.png
  • x_button_blue2.png
  • E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
  • zN7GBFwfMP4uA6AR0HCoLQ.ttf
  • 160229_chromecast_right_new2.jpg
  • ads
  • js
  • rankingnum.gif
  • 160229_Google_footer.jpg
  • js
  • 160229_Google_left.jpg
  • bg_sidebar.png
  • a_30_718.js
  • gizmodo.js
  • quant.js
  • aw.js
  • mediagene-22_4cf71447-cec0-49bb-aaca-3da6ab925bcc.js
  • pixel;r=273648601;a=p-JPy4_sPwwqa2N;fpan=1;fpa=P0-1561959601-1456748033512;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456748033511;tzo=-180;ref=;;ogl=
  • popin_discovery5-min.js
  • aps-adserving.min.js
  • ps-spr-1-mobile-jp.png
  • aps-base.min.css
  • ps-spr-2-mobile-jp.png
  • log.gif
  • 1573506583.json
  • rep
  • ui

Our browser made a total of 130 requests to load all elements on the main page. We found that 32% of them (42 requests) were addressed to the original, 5% (7 requests) were made to and 5% (6 requests) were made to The less responsive or slowest element that took the longest time to load (579 ms) relates to the external source

Additional info on


The browser has sent 124 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 39 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.











Possible request optimization













Normal result


As for redirects, our browser was forwarded to before it reached this domain.

IP address uses IP addresses which are currently shared with 14 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 60
A 60
A 60
A 60
NS 86400

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 96.3% of all visits is Japan. It lies approximately 4830 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up page load time for the majority of users is moving the server to Japan or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

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

Language and encoding

Normal result


JA ja language flag


N/A  language flag





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

Share this report in social media

Analyze another website