Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

rum.pt

Home · RUM

Page Load Speed

1.9 sec in total

First Response

197 ms

Resources Loaded

1.6 sec

Page Rendered

133 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 197 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 35% of websites can load faster.

Performance Metrics

rum.pt performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

rum.pt

197 ms

5c5882912abb2fb21400ba174efa53b1275d1e7b.css

162 ms

bedb66442813afde52b1904979046bb36d2e7eaa.js

672 ms

css

24 ms

modernizr.min.js

6 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 41% of them (9 requests) were addressed to the original Rum.pt, 14% (3 requests) were made to Google-analytics.com and 9% (2 requests) were made to Query.yahooapis.com. The less responsive or slowest element that took the longest time to load (672 ms) belongs to the original domain Rum.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.8 kB (30%)

Content Size

68.6 kB

After Optimization

47.8 kB

In fact, the total size of Rum.pt main page is 68.6 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 50.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 14.2 kB

  • Original 17.7 kB
  • After minification 13.2 kB
  • After compression 3.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 4.5 kB, which is 26% 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 14.2 kB or 80% of the original size.

JavaScript Optimization

-13%

Potential reduce by 6.6 kB

  • Original 50.9 kB
  • After minification 50.9 kB
  • After compression 44.2 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 6.6 kB or 13% of the original size.

Requests Breakdown

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

Requests Now

14

After Optimization

9

The browser has sent 14 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.

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

83

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

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

    N/A

  • 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 neither this language nor any other was claimed in <html> or <meta> tags. 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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: