Tools & Wizards About Us
roam.be screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

roam.be

Roam | We supply robust tools to help you build a better business

Page Load Speed

1.8 sec in total

First Response

280 ms

Resources Loaded

1.2 sec

Page Rendered

360 ms

roam.be screenshot

About Website

Welcome to roam.be homepage info - get ready to check Roam best content right away, or after learning these important things about roam.be

Roam is a webdesign and development business operated by Kevin Wetzels. The office is located in Tongeren, Belgium.

Visit roam.be

Key Findings

We analyzed Roam.be page load time and found that the first response time was 280 ms and then it took 1.5 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

roam.be performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

roam.be

280 ms

css

21 ms

screen.css

271 ms

pygments.css

187 ms

logo.png

187 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Roam.be, 64% (16 requests) were made to Static.roam.be and 16% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (796 ms) relates to the external source Static.roam.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.8 kB (15%)

Content Size

924.4 kB

After Optimization

782.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Roam.be main page is 924.4 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. 30% of websites need less resources to load. Images take 868.8 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 11.1 kB

  • Original 15.6 kB
  • After minification 12.3 kB
  • After compression 4.6 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 3.4 kB, which is 22% 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 11.1 kB or 71% of the original size.

Image Optimization

-13%

Potential reduce by 112.5 kB

  • Original 868.8 kB
  • After minification 756.3 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, Roam needs image optimization as it can save up to 112.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-80%

Potential reduce by 18.2 kB

  • Original 22.8 kB
  • After minification 15.9 kB
  • After compression 4.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. Roam.be needs all CSS files to be minified and compressed as it can save up to 18.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (15%)

Requests Now

20

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

roam.be

roam.be

280 ms

css

css

21 ms

screen.css

screen.css

271 ms

pygments.css

pygments.css

187 ms

logo.png

logo.png

187 ms

bold.io.png

bold.io.png

377 ms

svn-mailing.png

svn-mailing.png

449 ms

bsk.be.2.png

bsk.be.2.png

547 ms

extractor.png

extractor.png

449 ms

morse.png

morse.png

796 ms

ga.js

ga.js

99 ms

bg.png

bg.png

101 ms

builder.jpg

builder.jpg

264 ms

light.png

light.png

176 ms

monitor.png

monitor.png

262 ms

tag.png

tag.png

262 ms

dialog.png

dialog.png

260 ms

network-icons.png

network-icons.png

346 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAPWGQyH.woff

tDbI2oqRg1oM3QBjjcaDkOr9rAPWGQyH.woff

20 ms

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwetT0rU.woff

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwetT0rU.woff

20 ms

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGC6FRUI.woff

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGC6FRUI.woff

42 ms

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTmjW7BA.woff

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTmjW7BA.woff

65 ms

__utm.gif

__utm.gif

17 ms

print.css

print.css

89 ms

__utm.gif

__utm.gif

4 ms

Accessibility Review

roam.be accessibility score

95

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.

Best Practices

roam.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

roam.be 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 Roam.be 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 Roam.be 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

roam.be

Open Graph description is not detected on the main page of Roam. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: