Tools & Wizards About Us
gigaan.jp screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

gigaan.jp

レンタルサーバー｜ギガーン

Page Load Speed

4.8 sec in total

First Response

537 ms

Resources Loaded

4.1 sec

Page Rendered

181 ms

gigaan.jp screenshot

About Website

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

高機能・大容量レンタルサーバー。マルチドメイン標準装備。99.99%安定稼働、メールアドレス無制限、ウイルスチェック、携帯サイト、専用SSL、メールフォームなどビジネスに必要な全機能を網羅。ネッショップにも最適です。

Visit gigaan.jp

Key Findings

We analyzed Gigaan.jp page load time and found that the first response time was 537 ms and then it took 4.2 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

gigaan.jp performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.143

78/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

gigaan.jp

537 ms

www.gigaan.jp

1025 ms

import.css

167 ms

jquery.min.js

19 ms

shift.js

331 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 82% of them (53 requests) were addressed to the original Gigaan.jp, 6% (4 requests) were made to Googletagmanager.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Gigaan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.8 kB (20%)

Content Size

498.9 kB

After Optimization

399.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gigaan.jp main page is 498.9 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. 40% of websites need less resources to load. Images take 315.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.4 kB

  • Original 29.8 kB
  • After minification 24.1 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 19% 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 22.4 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 299 B

  • Original 315.0 kB
  • After minification 314.7 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. Gigaan images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 9.7 kB

  • Original 74.9 kB
  • After minification 70.6 kB
  • After compression 65.2 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 9.7 kB or 13% of the original size.

CSS Optimization

-85%

Potential reduce by 67.4 kB

  • Original 79.2 kB
  • After minification 54.5 kB
  • After compression 11.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. Gigaan.jp needs all CSS files to be minified and compressed as it can save up to 67.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (37%)

Requests Now

63

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gigaan.jp

gigaan.jp

537 ms

www.gigaan.jp

www.gigaan.jp

1025 ms

import.css

import.css

167 ms

jquery.min.js

jquery.min.js

19 ms

shift.js

shift.js

331 ms

common.js

common.js

496 ms

gtm.js

gtm.js

499 ms

base.css

base.css

349 ms

base_new.css

base_new.css

350 ms

top.css

top.css

494 ms

content.css

content.css

660 ms

entrydata.css

entrydata.css

663 ms

textstyle.css

textstyle.css

511 ms

logo_rakuslightcloud.svg

logo_rakuslightcloud.svg

184 ms

logo_gigaan.gif

logo_gigaan.gif

187 ms

header_tel.gif

header_tel.gif

187 ms

header_btn_pamph.gif

header_btn_pamph.gif

187 ms

g_navi_feature.gif

g_navi_feature.gif

186 ms

g_navi_price.gif

g_navi_price.gif

185 ms

g_navi_entry.gif

g_navi_entry.gif

519 ms

g_navi_support.gif

g_navi_support.gif

520 ms

g_navi_instance.gif

g_navi_instance.gif

520 ms

g_navi_faq.gif

g_navi_faq.gif

520 ms

gigaan_img.jpg

gigaan_img.jpg

884 ms

costperformance_title.jpg

costperformance_title.jpg

521 ms

course_off.jpg

course_off.jpg

521 ms

btn_xunit_off.jpg

btn_xunit_off.jpg

522 ms

giga_title.jpg

giga_title.jpg

540 ms

3giga_off.jpg

3giga_off.jpg

542 ms

ssl_off.jpg

ssl_off.jpg

713 ms

multidomain_off.jpg

multidomain_off.jpg

670 ms

index-copy-img.gif

index-copy-img.gif

669 ms

banner-xunit_off.jpg

banner-xunit_off.jpg

714 ms

banner-xbit_off.jpg

banner-xbit_off.jpg

724 ms

news_title.jpg

news_title.jpg

844 ms

btn_newslist_off.jpg

btn_newslist_off.jpg

844 ms

point.gif

point.gif

884 ms

others_title.jpg

others_title.jpg

884 ms

senyo.jpg

senyo.jpg

894 ms

kyoyo.jpg

kyoyo.jpg

1013 ms

form.jpg

form.jpg

1012 ms

requestBTN_off.gif

requestBTN_off.gif

1055 ms

faq_off.jpg

faq_off.jpg

1061 ms

btn_info.gif

btn_info.gif

1050 ms

domain1.gif

domain1.gif

1071 ms

mitsumori_off.jpg

mitsumori_off.jpg

1186 ms

toiawase_off.jpg

toiawase_off.jpg

1184 ms

WP-Chorus.png

WP-Chorus.png

1218 ms

gtm.js

gtm.js

102 ms

dairiten_b_off.gif

dairiten_b_off.gif

1179 ms

destination

destination

39 ms

destination

destination

95 ms

bat.js

bat.js

94 ms

bi.js

bi.js

859 ms

fbevents.js

fbevents.js

90 ms

uwt.js

uwt.js

78 ms

symantec.jpg

symantec.jpg

1060 ms

back2.gif

back2.gif

1068 ms

bg_content.gif

bg_content.gif

1178 ms

domain2.gif

domain2.gif

1177 ms

domain3.gif

domain3.gif

1211 ms

js

js

69 ms

adsct

adsct

171 ms

adsct

adsct

149 ms

pd.js

pd.js

242 ms

Accessibility Review

gigaan.jp accessibility score

72

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

gigaan.jp SEO score

77

Search Engine Optimization Advices

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

gigaan.jp

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