Tools & Wizards About Us
gigazine.net screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

gigazine.net

GIGAZINE（ギガジン） - 「VTuberってこんなにたくさんいるの？」と思わず驚くほど企業勢から個人勢までさまざまなVTuberをワンフェス2024[夏]で見かけたよまとめ

Page Load Speed

2.4 sec in total

First Response

31 ms

Resources Loaded

1.7 sec

Page Rendered

677 ms

gigazine.net screenshot

About Website

Visit gigazine.net now to see the best up-to-date GIGAZINE content for Japan and also check out these interesting facts you probably never knew about gigazine.net

日々のあらゆるシーンで役立つ情報を提供するIT系ニュースサイト。毎日更新中。

Visit gigazine.net

Key Findings

We analyzed Gigazine.net page load time and found that the first response time was 31 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

gigazine.net performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value3,010 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

gigazine.net

31 ms

gigazine.net

43 ms

common_v5_15.css

61 ms

jquery.min.js

47 ms

lazysizes.min.js

787 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Gigazine.net, 36% (16 requests) were made to I.gzn.jp and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (787 ms) relates to the external source I.gzn.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.9 kB (11%)

Content Size

951.1 kB

After Optimization

847.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gigazine.net main page is 951.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. 65% of websites need less resources to load. Javascripts take 620.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 71.8 kB

  • Original 97.7 kB
  • After minification 97.7 kB
  • After compression 25.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 71.8 kB or 74% of the original size.

Image Optimization

-14%

Potential reduce by 31.2 kB

  • Original 225.3 kB
  • After minification 194.1 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, GIGAZINE needs image optimization as it can save up to 31.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 888 B

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

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 7.9 kB
  • After minification 7.9 kB
  • After compression 7.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. Gigazine.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (63%)

Requests Now

43

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gigazine.net

gigazine.net

31 ms

gigazine.net

gigazine.net

43 ms

common_v5_15.css

common_v5_15.css

61 ms

jquery.min.js

jquery.min.js

47 ms

lazysizes.min.js

lazysizes.min.js

787 ms

index.min.js

index.min.js

45 ms

gpt.js

gpt.js

117 ms

-side-ad.js

-side-ad.js

686 ms

adsbygoogle.js

adsbygoogle.js

152 ms

OneSignalSDK.js

OneSignalSDK.js

77 ms

onesignal.js

onesignal.js

99 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

93 ms

gtm.js

gtm.js

80 ms

apstag.js

apstag.js

27 ms

6uu7uylb7t

6uu7uylb7t

74 ms

visa.png

visa.png

37 ms

master.png

master.png

683 ms

amex.png

amex.png

36 ms

apple-pay.svg

apple-pay.svg

37 ms

g-pay.png

g-pay.png

71 ms

push_button_off.png

push_button_off.png

72 ms

push_button.png

push_button.png

74 ms

snsicon2.png

snsicon2.png

76 ms

00_m.jpg

00_m.jpg

75 ms

00_m.png

00_m.png

74 ms

00.jpg

00.jpg

76 ms

pubads_impl.js

pubads_impl.js

44 ms

clarity.js

clarity.js

37 ms

js

js

98 ms

uwt.js

uwt.js

93 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

281 ms

analytics.js

analytics.js

265 ms

4330625

4330625

279 ms

collect

collect

41 ms

collect

collect

42 ms

adsct

adsct

183 ms

adsct

adsct

187 ms

ga-audiences

ga-audiences

39 ms

show_ads_impl.js

show_ads_impl.js

246 ms

caticons.png

caticons.png

543 ms

matomo.js

matomo.js

72 ms

fbevents.js

fbevents.js

19 ms

317312854340208

317312854340208

68 ms

matomo.php

matomo.php

536 ms

c.gif

c.gif

7 ms

Accessibility Review

gigazine.net accessibility score

81

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

gigazine.net best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gigazine.net SEO score

85

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

Content Best Practices

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

Impact

Issue

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 Gigazine.net 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 Gigazine.net 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

gigazine.net

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