Tools & Wizards About Us
remotely.fm screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

remotely.fm

Remotely - Record remote interviews that look & sound incredible

Page Load Speed

1.8 sec in total

First Response

111 ms

Resources Loaded

702 ms

Page Rendered

994 ms

remotely.fm screenshot

About Website

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

Remotely is the platform content creators use to easily record remote interviews in studio quality. Nothing to install. Just hit record.

Visit remotely.fm

Key Findings

We analyzed Remotely.fm page load time and found that the first response time was 111 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

remotely.fm performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value30.4 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value14,900 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.165

71/100

15%

TTI (Time to Interactive)

Value33.7 s

0/100

10%

Network Requests Diagram

remotely.fm

111 ms

l.js

200 ms

paddle.js

96 ms

plausible.js

29 ms

app.31c4e3ff.css

209 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 45% of them (13 requests) were addressed to the original Remotely.fm, 17% (5 requests) were made to Client.crisp.chat and 17% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (376 ms) belongs to the original domain Remotely.fm.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.0 kB (8%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Remotely.fm main page is 2.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 33.1 kB

  • Original 46.0 kB
  • After minification 45.9 kB
  • After compression 12.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 33.1 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 117.0 kB

  • Original 2.0 MB
  • After minification 1.9 MB

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. Remotely images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 228 B

  • Original 76.1 kB
  • After minification 76.1 kB
  • After compression 75.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. This website has mostly compressed JavaScripts.

CSS Optimization

-20%

Potential reduce by 23.6 kB

  • Original 120.4 kB
  • After minification 120.4 kB
  • After compression 96.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. Remotely.fm needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (62%)

Requests Now

21

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

remotely.fm

remotely.fm

111 ms

l.js

l.js

200 ms

paddle.js

paddle.js

96 ms

plausible.js

plausible.js

29 ms

app.31c4e3ff.css

app.31c4e3ff.css

209 ms

client.js

client.js

219 ms

client_default.css

client_default.css

229 ms

animate.css

animate.css

195 ms

paddle.css

paddle.css

206 ms

Landing.chunk.d67eda39.css

Landing.chunk.d67eda39.css

216 ms

Landing.chunk.305260d4.js

Landing.chunk.305260d4.js

34 ms

js

js

63 ms

chunk-vendors.89aac3ca.js

chunk-vendors.89aac3ca.js

376 ms

app.6b143644.js

app.6b143644.js

33 ms

participants.35466210.png

participants.35466210.png

89 ms

audio-large.cd6aa665.png

audio-large.cd6aa665.png

372 ms

video-large.7bb53f48.png

video-large.7bb53f48.png

90 ms

schedule-large.6aea2a21.png

schedule-large.6aea2a21.png

233 ms

client.js

client.js

40 ms

client_legacy.css

client_legacy.css

56 ms

css

css

47 ms

wave-light.82bf7086.svg

wave-light.82bf7086.svg

228 ms

wave.78d038bb.svg

wave.78d038bb.svg

81 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff

146 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo3cOWxw.woff

146 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo3cOWxw.woff

173 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff

180 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdo3cOWxw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdo3cOWxw.woff

181 ms

element-icons.535877f5.woff

element-icons.535877f5.woff

124 ms

Accessibility Review

remotely.fm accessibility score

82

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

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

remotely.fm best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

remotely.fm SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Remotely.fm can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Remotely.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

remotely.fm

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