Tools & Wizards About Us
firestorage.jp screenshot

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.1 MB (52%)

Content Size

2.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Firestorage.jp main page is 2.1 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.2 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

-49%

Potential reduce by 575.2 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 595.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 575.2 kB or 49% 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

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

firestorage.jp

firestorage.jp

1182 ms

js

js

66 ms

main2018.js

main2018.js

1021 ms

swfTagWriter.js

swfTagWriter.js

872 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

1235 ms

jquery.ui.widget.js

jquery.ui.widget.js

1070 ms

jquery.iframe-transport.js

jquery.iframe-transport.js

903 ms

jquery.fileupload.js

jquery.fileupload.js

1255 ms

upload2021ssl.js

upload2021ssl.js

1034 ms

clipboard.min.js

clipboard.min.js

1071 ms

axios.min.js

axios.min.js

1084 ms

uketoru_mini_top.js

uketoru_mini_top.js

921 ms

basic.css

basic.css

1343 ms

style2011_2.css

style2011_2.css

1197 ms

reset.css

reset.css

1244 ms

top.css

top.css

1244 ms

wrapper.min.js

wrapper.min.js

735 ms

ad.cgi

ad.cgi

907 ms

js

js

41 ms

js

js

101 ms

ad.cgi

ad.cgi

747 ms

adsbygoogle.js

adsbygoogle.js

154 ms

news.cgi

news.cgi

752 ms

gpt.js

gpt.js

150 ms

ad.cgi

ad.cgi

869 ms

analytics.js

analytics.js

81 ms

collect

collect

38 ms

collect

collect

31 ms

collect

collect

32 ms

ga-audiences

ga-audiences

42 ms

uketoru_botton.png

uketoru_botton.png

888 ms

uketoru_top1.png

uketoru_top1.png

1087 ms

bar.gif

bar.gif

676 ms

fd_foot_win.png

fd_foot_win.png

1477 ms

header_bg_new.jpg

header_bg_new.jpg

232 ms

logo_fire.png

logo_fire.png

232 ms

icon_fire.png

icon_fire.png

231 ms

new.gif

new.gif

234 ms

drive_web.gif

drive_web.gif

233 ms

information.gif

information.gif

233 ms

page_add.gif

page_add.gif

385 ms

date.gif

date.gif

385 ms

comment.png

comment.png

430 ms

mouse.png

mouse.png

428 ms

cuts.png

cuts.png

427 ms

pencil_add.png

pencil_add.png

428 ms

calendar.png

calendar.png

560 ms

lock.gif

lock.gif

560 ms

bullet_go.png

bullet_go.png

670 ms

upload_screen_shot_gray.png

upload_screen_shot_gray.png

671 ms

disk_multiple.gif

disk_multiple.gif

671 ms

pencil_add.gif

pencil_add.gif

672 ms

music.gif

music.gif

678 ms

add.gif

add.gif

678 ms

cancel.gif

cancel.gif

847 ms

banner_news.png

banner_news.png

852 ms

banner_about.jpg

banner_about.jpg

848 ms

con2.jpg

con2.jpg

849 ms

image_plan.jpg

image_plan.jpg

843 ms

image_why.jpg

image_why.jpg

843 ms

con5.jpg

con5.jpg

1070 ms

macfan9.gif

macfan9.gif

1069 ms

macpeople20100729.jpg

macpeople20100729.jpg

1075 ms

ascii201112.jpg

ascii201112.jpg

1073 ms

cnet6.png

cnet6.png

1073 ms

spa123.gif

spa123.gif

1077 ms

gigazine.png

gigazine.png

1269 ms

wedding-cinderella.png

wedding-cinderella.png

1270 ms

rocketnews24.png

rocketnews24.png

1290 ms

2024_orange_button.png

2024_orange_button.png

424 ms

k40-1.png

k40-1.png

610 ms

k40-2.png

k40-2.png

613 ms

k40-3.png

k40-3.png

667 ms

65.jpg

65.jpg

597 ms

1x1.gif

1x1.gif

991 ms

kaz-name.png

kaz-name.png

1275 ms

42.gif

42.gif

526 ms

1x1.gif

1x1.gif

1040 ms

show_ads_impl.js

show_ads_impl.js

247 ms

pubads_impl.js

pubads_impl.js

13 ms

ft1.gif

ft1.gif

1064 ms

ft2.gif

ft2.gif

1066 ms

ft3.gif

ft3.gif

1122 ms

ft5.gif

ft5.gif

1122 ms

btn_japan_lang.jpg

btn_japan_lang.jpg

1241 ms

9176203

9176203

158 ms

gnav_bg.jpg

gnav_bg.jpg

1201 ms

1x1.gif

1x1.gif

800 ms

1x1.gif

1x1.gif

807 ms

flashup.cgi

flashup.cgi

801 ms

fabi.gif

fabi.gif

1089 ms

about2.jpg

about2.jpg

1072 ms

excite_logo.jpg

excite_logo.jpg

1088 ms

guide.gif

guide.gif

1089 ms

check.gif

check.gif

1130 ms

footer_top.jpg

footer_top.jpg

1130 ms

uid2SecureSignal.js

uid2SecureSignal.js

138 ms

publishertag.ids.js

publishertag.ids.js

127 ms

esp.js

esp.js

153 ms

pubcid.min.js

pubcid.min.js

146 ms

ads

ads

361 ms

container.html

container.html

153 ms

ftf1.gif

ftf1.gif

999 ms

ftf2.gif

ftf2.gif

1014 ms

zrt_lookup.html

zrt_lookup.html

141 ms

ads

ads

690 ms

ads

ads

258 ms

ftf3.gif

ftf3.gif

1007 ms

ftf4.gif

ftf4.gif

1007 ms

ftf8.gif

ftf8.gif

1055 ms

camera_add.gif

camera_add.gif

1055 ms

ftf9.gif

ftf9.gif

1048 ms

ftf10.gif

ftf10.gif

1063 ms

ftf12.gif

ftf12.gif

996 ms

upload_dd.jpg

upload_dd.jpg

997 ms

upload_button.png

upload_button.png

1045 ms

15056026655734612032

15056026655734612032

272 ms

icon.png

icon.png

71 ms

abg_lite.js

abg_lite.js

87 ms

s

s

72 ms

window_focus.js

window_focus.js

83 ms

qs_click_protection.js

qs_click_protection.js

90 ms

ufs_web_display.js

ufs_web_display.js

74 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

253 ms

activeview

activeview

76 ms

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

4 ms

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

firestorage.jp

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: