Tools & Wizards About Us
replay.sh screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

replay.sh

Rewind Backups for SaaS Apps

Page Load Speed

2.3 sec in total

First Response

63 ms

Resources Loaded

1.2 sec

Page Rendered

1.1 sec

replay.sh screenshot

About Website

Click here to check amazing Replay content. Otherwise, check out these important facts you probably never knew about replay.sh

Protect your mission-critical SaaS data now with Rewind Backups. We make data protection easier for ecommerce, development, accounting & more.

Visit replay.sh

Key Findings

We analyzed Replay.sh page load time and found that the first response time was 63 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

replay.sh performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value2,880 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

replay.sh

63 ms

rewind.com

165 ms

css2

34 ms

147 ms

script.js

121 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Replay.sh, 62% (48 requests) were made to Rewind.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (577 ms) relates to the external source Rewind.com.

Page Optimization Overview & Recommendations

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

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Replay.sh 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. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 179.4 kB

  • Original 219.5 kB
  • After minification 188.3 kB
  • After compression 40.0 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. This page needs HTML code to be minified as it can gain 31.2 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 179.4 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.9 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. Replay images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 8.2 kB

  • Original 135.1 kB
  • After minification 135.1 kB
  • After compression 126.8 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.

Requests Breakdown

Number of requests can be reduced by 35 (50%)

Requests Now

70

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

replay.sh

replay.sh

63 ms

rewind.com

rewind.com

165 ms

css2

css2

34 ms

147 ms

script.js

script.js

121 ms

js.cookie.min.js

js.cookie.min.js

24 ms

optimize.js

optimize.js

53 ms

v2.js

v2.js

36 ms

embed2.js

embed2.js

22 ms

298 ms

gtm.js

gtm.js

193 ms

check-blue.svg

check-blue.svg

245 ms

RWD_Homepage_Product_Carousel.png

RWD_Homepage_Product_Carousel.png

113 ms

glossier-logo-dark.svg

glossier-logo-dark.svg

111 ms

lutron_logo_22-300x79.png

lutron_logo_22-300x79.png

119 ms

mailonline-dark-300x103.png

mailonline-dark-300x103.png

126 ms

amplitude-dark-300x103.png

amplitude-dark-300x103.png

122 ms

Moomin-logo-black2-300x90.png

Moomin-logo-black2-300x90.png

123 ms

olaplex-300x64.png

olaplex-300x64.png

243 ms

circle-arrow-left.svg

circle-arrow-left.svg

131 ms

circle-arrow-right.svg

circle-arrow-right.svg

167 ms

platform-icons-shopify.svg

platform-icons-shopify.svg

165 ms

platform-icons-jira.svg

platform-icons-jira.svg

168 ms

platform-icons-github.svg

platform-icons-github.svg

238 ms

platform-icons-klaviyo.svg

platform-icons-klaviyo.svg

298 ms

platform-icons-mailchimp.svg

platform-icons-mailchimp.svg

239 ms

platform-icons-bigcommerce.svg

platform-icons-bigcommerce.svg

238 ms

platform-icons-confluence.svg

platform-icons-confluence.svg

270 ms

quickbooks-logo.svg

quickbooks-logo.svg

358 ms

platform-icons-bitbucket.svg

platform-icons-bitbucket.svg

269 ms

platform-icons-trello.svg

platform-icons-trello.svg

268 ms

platform-icons-azure-devops.svg

platform-icons-azure-devops.svg

266 ms

platform-icons-okta.svg

platform-icons-okta.svg

434 ms

Headshot.png

Headshot.png

477 ms

NickLococo_RXSG.png

NickLococo_RXSG.png

480 ms

platform-icons-quickbooks.svg

platform-icons-quickbooks.svg

299 ms

Geni-Whitehouse.png

Geni-Whitehouse.png

480 ms

Testimonial_Scott_Simpletivity.png

Testimonial_Scott_Simpletivity.png

500 ms

qbo-general-features.png

qbo-general-features.png

436 ms

product-image-collaboration.png

product-image-collaboration.png

478 ms

product-image-vault.png

product-image-vault.png

476 ms

CloudDataSecurity_EasiestAdmin_EaseOfAdmin.svg

CloudDataSecurity_EasiestAdmin_EaseOfAdmin.svg

577 ms

CloudDataSecurity_EasiestSetup_EaseOfSetup.svg

CloudDataSecurity_EasiestSetup_EaseOfSetup.svg

502 ms

CloudDataSecurity_EasiestToDoBusinessWith_EaseOfDoingBusinessWith.svg

CloudDataSecurity_EasiestToDoBusinessWith_EaseOfDoingBusinessWith.svg

500 ms

CloudDataSecurity_HighPerformer_HighPerformer.svg

CloudDataSecurity_HighPerformer_HighPerformer.svg

512 ms

SaaSBackup_MomentumLeader_Leader.svg

SaaSBackup_MomentumLeader_Leader.svg

429 ms

RWD_BlogIllustration_CyberResilience_Header-1024x538.jpg

RWD_BlogIllustration_CyberResilience_Header-1024x538.jpg

439 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EL7I.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EL7I.woff

88 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EL7I.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkW-EL7I.woff

161 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODL7I.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkYODL7I.woff

192 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDL7I.woff

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkbqDL7I.woff

220 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

7 ms

RWD_State_of_Cybersecurity_in_2023_Header-1024x576.png

RWD_State_of_Cybersecurity_in_2023_Header-1024x576.png

413 ms

icon-play.svg

icon-play.svg

409 ms

what-is-headless-thumb-1024x576.jpeg

what-is-headless-thumb-1024x576.jpeg

530 ms

facebook.svg

facebook.svg

411 ms

instagram.svg

instagram.svg

415 ms

linkedin.svg

linkedin.svg

409 ms

twitter.svg

twitter.svg

404 ms

youtube.svg

youtube.svg

384 ms

destination

destination

123 ms

6865219.js

6865219.js

182 ms

growsumo.min.js

growsumo.min.js

260 ms

tags.js

tags.js

285 ms

uwt.js

uwt.js

156 ms

fbevents.js

fbevents.js

163 ms

u

u

387 ms

gutchrhv

gutchrhv

394 ms

js

js

157 ms

collectedforms.js

collectedforms.js

119 ms

web-interactives-embed.js

web-interactives-embed.js

160 ms

banner.js

banner.js

156 ms

leadflows.js

leadflows.js

121 ms

6865219.js

6865219.js

141 ms

adsct

adsct

114 ms

adsct

adsct

213 ms

tracking.min.js

tracking.min.js

181 ms

Accessibility Review

replay.sh accessibility score

89

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 have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

replay.sh 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

Page has valid source maps

SEO Factors

replay.sh SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Replay.sh 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 Replay.sh 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

replay.sh

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