Tools & Wizards About Us
rum.pt screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

rum.pt

Home · RUM

Page Load Speed

3.1 sec in total

First Response

179 ms

Resources Loaded

2.4 sec

Page Rendered

484 ms

rum.pt screenshot

About Website

Welcome to rum.pt homepage info - get ready to check RUM best content for Portugal right away, or after learning these important things about rum.pt

Rádio Universitária do Minho

Visit rum.pt

Key Findings

We analyzed Rum.pt page load time and found that the first response time was 179 ms and then it took 2.9 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

rum.pt performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

rum.pt

179 ms

rum.pt

1213 ms

css

39 ms

js

58 ms

66b0b65ee0829d09851d9042-NjQtNjAyNi5qcGVn.jpeg

607 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 71% of them (12 requests) were addressed to the original Rum.pt, 12% (2 requests) were made to Fonts.gstatic.com and 6% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Rum.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 456.3 kB (65%)

Content Size

701.8 kB

After Optimization

245.6 kB

  • HTML
  • Images

In fact, the total size of Rum.pt main page is 701.8 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. 35% of websites need less resources to load. HTML takes 544.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 452.6 kB

  • Original 544.6 kB
  • After minification 542.7 kB
  • After compression 92.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. 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 452.6 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 3.6 kB

  • Original 157.2 kB
  • After minification 153.6 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. RUM images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 5 (56%)

Requests Now

9

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rum.pt

rum.pt

179 ms

rum.pt

rum.pt

1213 ms

css

css

39 ms

js

js

58 ms

66b0b65ee0829d09851d9042-NjQtNjAyNi5qcGVn.jpeg

66b0b65ee0829d09851d9042-NjQtNjAyNi5qcGVn.jpeg

607 ms

15e1003ad72644371566.js

15e1003ad72644371566.js

84 ms

350a69ebf9a1e6cd5215.js

350a69ebf9a1e6cd5215.js

273 ms

9896eae7cc12e911dd53.js

9896eae7cc12e911dd53.js

499 ms

4c61ded7d1dcf037e2dc.js

4c61ded7d1dcf037e2dc.js

717 ms

96ac9c69b29a888e2d72.js

96ac9c69b29a888e2d72.js

648 ms

rum.pt

rum.pt

1058 ms

e3debf9.woff

e3debf9.woff

436 ms

6382761.woff

6382761.woff

394 ms

5ee0fbd.woff

5ee0fbd.woff

220 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

23 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

37 ms

e8a6d8f.woff

e8a6d8f.woff

276 ms

Accessibility Review

rum.pt accessibility score

86

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

Links do not have a discernible name

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

rum.pt 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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rum.pt SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

rum.pt

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