Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

gigapod.jp

GIGAPOD5 | ファイル転送からオフィスの統合的ファイル共有ソリューションへ トライポッドワークス株式会社

Page Load Speed

8.9 sec in total

First Response

413 ms

Resources Loaded

7.9 sec

Page Rendered

574 ms

gigapod.jp screenshot

About Website

Welcome to gigapod.jp homepage info - get ready to check Gigapod best content for Guinea right away, or after learning these important things about gigapod.jp

電子メールの添付ファイルはもう受け取らない、送らない。次世代型オンラインストレージ「GIGAPOD5」

Visit gigapod.jp

Key Findings

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

Performance Metrics

gigapod.jp performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.499

16/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

gigapod.jp

413 ms

790 ms

all.js

422 ms

import.css

333 ms

nav.css

335 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gigapod.jp, 78% (95 requests) were made to Tripodworks.co.jp and 7% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Tripodworks.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 577.2 kB (39%)

Content Size

1.5 MB

After Optimization

899.6 kB

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

HTML Optimization

-72%

Potential reduce by 33.9 kB

  • Original 47.4 kB
  • After minification 46.8 kB
  • After compression 13.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. 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 33.9 kB or 72% of the original size.

Image Optimization

-11%

Potential reduce by 80.5 kB

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

JavaScript Optimization

-54%

Potential reduce by 208.0 kB

  • Original 387.2 kB
  • After minification 382.1 kB
  • After compression 179.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 208.0 kB or 54% of the original size.

CSS Optimization

-83%

Potential reduce by 254.7 kB

  • Original 306.7 kB
  • After minification 290.6 kB
  • After compression 51.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. Gigapod.jp needs all CSS files to be minified and compressed as it can save up to 254.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (26%)

Requests Now

118

After Optimization

87

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

Accessibility Review

gigapod.jp accessibility score

61

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

gigapod.jp 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

gigapod.jp SEO score

92

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

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

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

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