Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 53% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

retros.work

Online retrospective tool for scrum agile teams | Retros.work

Page Load Speed

2.7 sec in total

First Response

144 ms

Resources Loaded

1.8 sec

Page Rendered

712 ms

retros.work screenshot

About Website

Click here to check amazing Retros content. Otherwise, check out these important facts you probably never knew about retros.work

Online retrospective board for your remote team. Add feedback with emoticons, text and scores. Vote. Analyse trends. Custom questions. It's free.

Visit retros.work

Key Findings

We analyzed Retros.work page load time and found that the first response time was 144 ms and then it took 2.5 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

retros.work performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value2,920 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

retros.work

144 ms

retros.work

472 ms

style.css

144 ms

js

82 ms

cookies.js

217 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 21% of them (6 requests) were addressed to the original Retros.work, 24% (7 requests) were made to Unpkg.com and 17% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (472 ms) belongs to the original domain Retros.work.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.2 kB (22%)

Content Size

327.7 kB

After Optimization

254.5 kB

In fact, the total size of Retros.work main page is 327.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 178.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 70.7 kB

  • Original 90.4 kB
  • After minification 75.5 kB
  • After compression 19.7 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 14.9 kB, which is 16% 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 70.7 kB or 78% of the original size.

JavaScript Optimization

-1%

Potential reduce by 2.6 kB

  • Original 178.9 kB
  • After minification 178.9 kB
  • After compression 176.3 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

-0%

Potential reduce by 0 B

  • Original 58.4 kB
  • After minification 58.4 kB
  • After compression 58.4 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. Retros.work has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (63%)

Requests Now

19

After Optimization

7

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

Accessibility Review

retros.work accessibility score

82

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

Best Practices

retros.work 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

High

Page has valid source maps

SEO Factors

retros.work SEO score

100

Search Engine Optimization Advices

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