Tools & Wizards About Us
files.fm screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

files.fm

File upload & sharing. Send large photos and videos. Online cloud storage.

Page Load Speed

3.1 sec in total

First Response

20 ms

Resources Loaded

1.9 sec

Page Rendered

1.2 sec

files.fm screenshot

About Website

Click here to check amazing File S content for United States. Otherwise, check out these important facts you probably never knew about files.fm

File upload & sharing. Cloud file storage. Store, Share, Send or Sell your files, photos, videos, music and docs. Free signup.

Visit files.fm

Key Findings

We analyzed Files.fm page load time and found that the first response time was 20 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

files.fm performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

files.fm

20 ms

files.fm

811 ms

matomo.js

842 ms

js

49 ms

google_conversion.js

30 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 89% of them (119 requests) were addressed to the original Files.fm, 4% (5 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (842 ms) relates to the external source Analytics.files.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.8 kB (21%)

Content Size

1.0 MB

After Optimization

788.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Files.fm main page is 1.0 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. Only a small number of websites need less resources to load. Images take 450.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 123.9 kB

  • Original 155.8 kB
  • After minification 155.6 kB
  • After compression 31.8 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 123.9 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 450.4 kB
  • After minification 450.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. File S images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 45.5 kB

  • Original 304.4 kB
  • After minification 304.4 kB
  • After compression 258.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 45.5 kB or 15% of the original size.

CSS Optimization

-48%

Potential reduce by 44.4 kB

  • Original 92.1 kB
  • After minification 48.2 kB
  • After compression 47.6 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. Files.fm needs all CSS files to be minified and compressed as it can save up to 44.4 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (55%)

Requests Now

121

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

files.fm

files.fm

20 ms

files.fm

files.fm

811 ms

matomo.js

matomo.js

842 ms

js

js

49 ms

google_conversion.js

google_conversion.js

30 ms

reset.css

reset.css

27 ms

global.css

global.css

28 ms

header.css

header.css

33 ms

messages.css

messages.css

47 ms

chat.css

chat.css

42 ms

jquery-1.12.2.min.js

jquery-1.12.2.min.js

45 ms

jquery-migrate-1.3.0.js

jquery-migrate-1.3.0.js

89 ms

cycle.js

cycle.js

45 ms

error_handler_client

error_handler_client

415 ms

js

js

53 ms

analytics.js

analytics.js

20 ms

js

js

47 ms

js

js

161 ms

dropdown.css

dropdown.css

37 ms

global_facelift.css

global_facelift.css

16 ms

inputs.css

inputs.css

37 ms

jquery-ui.min.css

jquery-ui.min.css

38 ms

thickbox.css

thickbox.css

37 ms

modal.css

modal.css

43 ms

font-awesome.min.css

font-awesome.min.css

158 ms

light.min.css

light.min.css

43 ms

brands.min.css

brands.min.css

158 ms

fontawesome.min.css

fontawesome.min.css

161 ms

alert.css

alert.css

160 ms

jquery.cookie.js

jquery.cookie.js

162 ms

jquery-ui.js

jquery-ui.js

163 ms

global.js

global.js

162 ms

info_tooltips.js

info_tooltips.js

161 ms

jquery-ui.min.js

jquery-ui.min.js

164 ms

event.js

event.js

164 ms

functions.js

functions.js

168 ms

thickbox.js

thickbox.js

169 ms

modal.js

modal.js

171 ms

alert.js

alert.js

170 ms

LazyGoogleReCaptchaV2.js

LazyGoogleReCaptchaV2.js

168 ms

sign_in_form.css

sign_in_form.css

174 ms

uploadifive.css

uploadifive.css

169 ms

landing.css

landing.css

170 ms

client_detection.js

client_detection.js

169 ms

jquery.uploadifive.custom_folderupload.js

jquery.uploadifive.custom_folderupload.js

172 ms

index.js

index.js

173 ms

landing.js

landing.js

174 ms

collect

collect

126 ms

js

js

96 ms

collect

collect

207 ms

collect

collect

239 ms

pricing_v2.css

pricing_v2.css

132 ms

footer.css

footer.css

189 ms

inputs.js

inputs.js

131 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

343 ms

collect

collect

135 ms

burger_menu.svg

burger_menu.svg

75 ms

files-fm-logo-slogan.svg

files-fm-logo-slogan.svg

78 ms

globe.svg

globe.svg

80 ms

log_in.svg

log_in.svg

73 ms

log_in_blue.svg

log_in_blue.svg

71 ms

login-google.svg

login-google.svg

75 ms

login-microsoft.svg

login-microsoft.svg

142 ms

sign_up.svg

sign_up.svg

147 ms

login-facebook.svg

login-facebook.svg

144 ms

upload_cloud_red_comb.svg

upload_cloud_red_comb.svg

146 ms

edit_blue.svg

edit_blue.svg

141 ms

send.svg

send.svg

140 ms

upload_cloud_white.svg

upload_cloud_white.svg

157 ms

upload_cloud_white_arrow.svg

upload_cloud_white_arrow.svg

153 ms

Files.fm-cloud-storage-platform-Zavadskis.webp

Files.fm-cloud-storage-platform-Zavadskis.webp

161 ms

2-devices.webp

2-devices.webp

159 ms

home_filled.svg

home_filled.svg

154 ms

windows.svg

windows.svg

156 ms

android.svg

android.svg

175 ms

apple.svg

apple.svg

186 ms

LTRK.png

LTRK.png

177 ms

SPRK.png

SPRK.png

173 ms

LIKTA.png

LIKTA.png

174 ms

IT-cluster.png

IT-cluster.png

188 ms

arcers.png

arcers.png

188 ms

LFF.png

LFF.png

187 ms

ltv.png

ltv.png

189 ms

sigulda.png

sigulda.png

194 ms

eparaksts.png

eparaksts.png

195 ms

LVRTC.png

LVRTC.png

198 ms

fkmetta.png

fkmetta.png

212 ms

europe_h2020_program.png

europe_h2020_program.png

193 ms

microsoft_cloud_storage_partner.png

microsoft_cloud_storage_partner.png

197 ms

e-shelter.png

e-shelter.png

204 ms

lattelecom_tet_v2.png

lattelecom_tet_v2.png

212 ms

blockvis.com-logo.png

blockvis.com-logo.png

208 ms

ga-audiences

ga-audiences

119 ms

ga-audiences

ga-audiences

107 ms

AlbertSans-Regular.ttf

AlbertSans-Regular.ttf

146 ms

AlbertSans-Medium.ttf

AlbertSans-Medium.ttf

144 ms

AlbertSans-Light.ttf

AlbertSans-Light.ttf

184 ms

AlbertSans-ExtraLight.ttf

AlbertSans-ExtraLight.ttf

184 ms

AlbertSans-Thin.ttf

AlbertSans-Thin.ttf

224 ms

AlbertSans-SemiBold.ttf

AlbertSans-SemiBold.ttf

180 ms

AlbertSans-Bold.ttf

AlbertSans-Bold.ttf

120 ms

AlbertSans-ExtraBold.ttf

AlbertSans-ExtraBold.ttf

119 ms

AlbertSans-Black.ttf

AlbertSans-Black.ttf

118 ms

Roboto-Regular.woff

Roboto-Regular.woff

651 ms

Roboto-Bold.woff

Roboto-Bold.woff

680 ms

feature-1.webp

feature-1.webp

115 ms

feature-2.webp

feature-2.webp

108 ms

feature-3.webp

feature-3.webp

145 ms

feature-4.webp

feature-4.webp

147 ms

feature-5.webp

feature-5.webp

145 ms

feature-6.webp

feature-6.webp

142 ms

3-why-choose.webp

3-why-choose.webp

168 ms

arrow-down-button.svg

arrow-down-button.svg

162 ms

european-flag.svg

european-flag.svg

128 ms

dropdown_grey.svg

dropdown_grey.svg

128 ms

post_log

post_log

550 ms

transfer.svg

transfer.svg

151 ms

file_upload.svg

file_upload.svg

152 ms

images.svg

images.svg

152 ms

football.svg

football.svg

152 ms

cart.svg

cart.svg

150 ms

earth.svg

earth.svg

150 ms

convert_video.svg

convert_video.svg

151 ms

convert_pdf.svg

convert_pdf.svg

162 ms

videocall.svg

videocall.svg

160 ms

blob_6.png

blob_6.png

161 ms

blob_8.png

blob_8.png

168 ms

blob_3.png

blob_3.png

164 ms

check.svg

check.svg

161 ms

blob_2.png

blob_2.png

167 ms

arrow_down.svg

arrow_down.svg

161 ms

arrow_up.svg

arrow_up.svg

498 ms

loadingAnimation.gif

loadingAnimation.gif

136 ms

matomo.php

matomo.php

174 ms

Accessibility Review

files.fm accessibility score

88

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

files.fm 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

files.fm SEO score

93

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

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Files.fm can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Files.fm 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

files.fm

Open Graph data is detected on the main page of File S. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: