Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

firestorage.jp

容量無制限の無料オンラインストレージ firestorage

Page Load Speed

6.3 sec in total

First Response

1.2 sec

Resources Loaded

4.9 sec

Page Rendered

195 ms

firestorage.jp screenshot

About Website

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

登録不要で容量無制限のストレージ | リモートワーク・テレワークで大容量のファイルを送る時や長期保存、共有に便利です

Visit firestorage.jp

Key Findings

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

Performance Metrics

firestorage.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value7,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.217

57/100

15%

TTI (Time to Interactive)

Value43.5 s

0/100

10%

Network Requests Diagram

firestorage.jp

1182 ms

js

66 ms

main2018.js

1021 ms

swfTagWriter.js

872 ms

jquery-3.1.1.min.js

1235 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Firestorage.jp, 56% (71 requests) were made to Sakura1.firestorage.jp and 6% (7 requests) were made to Cdn.firestorage.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Images.firews.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (56%)

Content Size

2.3 MB

After Optimization

1.0 MB

In fact, the total size of Firestorage.jp 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. 70% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 40.6 kB

  • Original 52.5 kB
  • After minification 47.3 kB
  • After compression 11.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 40.6 kB or 77% of the original size.

Image Optimization

-50%

Potential reduce by 426.6 kB

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

JavaScript Optimization

-57%

Potential reduce by 775.5 kB

  • Original 1.4 MB
  • After minification 1.3 MB
  • After compression 595.7 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 775.5 kB or 57% of the original size.

CSS Optimization

-85%

Potential reduce by 69.0 kB

  • Original 80.8 kB
  • After minification 62.5 kB
  • After compression 11.8 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. Firestorage.jp needs all CSS files to be minified and compressed as it can save up to 69.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 74 (60%)

Requests Now

124

After Optimization

50

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

Accessibility Review

firestorage.jp accessibility score

85

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

firestorage.jp SEO score

71

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 Firestorage.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 Firestorage.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 data is detected on the main page of Firestorage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: