Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gigafile.nu

無料大容量 ファイル転送サービス GigaFile(ギガファイル)便

Page Load Speed

13.6 sec in total

First Response

1.2 sec

Resources Loaded

12 sec

Page Rendered

392 ms

gigafile.nu screenshot

About Website

Visit gigafile.nu now to see the best up-to-date Giga File content for Japan and also check out these interesting facts you probably never knew about gigafile.nu

無料大容量 ファイル転送サービス GigaFile(ギガファイル)便!「3日~100日」選べる7種類のファイルの保持期限に加え、1ファイル300Gまでアップロード、共有可能!もちろん容量無制限でアンチウイルス装備。会員登録も不要です。

Visit gigafile.nu

Key Findings

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

Performance Metrics

gigafile.nu performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value3,230 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

gigafile.nu

1201 ms

style_v4.css

528 ms

jquery-1.11.0.min.js

1058 ms

xdr.js

313 ms

chunk_upload.js

323 ms

Our browser made a total of 352 requests to load all elements on the main page. We found that 1% of them (5 requests) were addressed to the original Gigafile.nu, 10% (36 requests) were made to Src.gigafile.nu and 7% (23 requests) were made to Ads.contextweb.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Src.gigafile.nu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (48%)

Content Size

2.3 MB

After Optimization

1.2 MB

In fact, the total size of Gigafile.nu main page is 2.3 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 97.3 kB

  • Original 120.4 kB
  • After minification 115.3 kB
  • After compression 23.1 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 97.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 12.8 kB

  • Original 677.0 kB
  • After minification 664.2 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. Giga File images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 771.5 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 442.9 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 771.5 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 222.4 kB

  • Original 268.4 kB
  • After minification 262.3 kB
  • After compression 46.0 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. Gigafile.nu needs all CSS files to be minified and compressed as it can save up to 222.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 252 (79%)

Requests Now

319

After Optimization

67

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

Accessibility Review

gigafile.nu accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

gigafile.nu 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gigafile.nu SEO score

83

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gigafile.nu 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 Gigafile.nu 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 data is detected on the main page of Giga File. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: