Tools & Wizards About Us
ruter.no screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ruter.no

Ruter – kollektivtrafikk i Oslo og Akershus | Ruter

Page Load Speed

3.5 sec in total

First Response

464 ms

Resources Loaded

2.8 sec

Page Rendered

181 ms

ruter.no screenshot

About Website

Click here to check amazing Ruter content for Norway. Otherwise, check out these important facts you probably never knew about ruter.no

Her finner du rutetider, reiseplanlegger og billettinformasjon for kollektivtrafikken i Oslo og Akershus.

Visit ruter.no

Key Findings

We analyzed Ruter.no page load time and found that the first response time was 464 ms and then it took 3 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

ruter.no performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,480 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.433

22/100

15%

TTI (Time to Interactive)

Value11.0 s

20/100

10%

Network Requests Diagram

ruter.no

464 ms

bundle.css

1346 ms

ruter-logo--brand.png

303 ms

bundle-libraries.js

929 ms

bundle.js

527 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 78% of them (21 requests) were addressed to the original Ruter.no, 15% (4 requests) were made to Google-analytics.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ruter.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.8 kB (33%)

Content Size

210.7 kB

After Optimization

141.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ruter.no main page is 210.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. 20% of websites need less resources to load. Images take 124.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 52.7 kB

  • Original 63.3 kB
  • After minification 51.0 kB
  • After compression 10.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 12.3 kB, which is 19% 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 52.7 kB or 83% of the original size.

Image Optimization

-13%

Potential reduce by 16.1 kB

  • Original 124.3 kB
  • After minification 108.2 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, Ruter needs image optimization as it can save up to 16.1 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 93 B

  • Original 23.2 kB
  • After minification 23.2 kB
  • After compression 23.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.

Requests Breakdown

Number of requests can be reduced by 10 (45%)

Requests Now

22

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ruter. 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

ruter.no

ruter.no

464 ms

bundle.css

bundle.css

1346 ms

ruter-logo--brand.png

ruter-logo--brand.png

303 ms

bundle-libraries.js

bundle-libraries.js

929 ms

bundle.js

bundle.js

527 ms

toppfoto_brynstunnelen_767x250.jpg

toppfoto_brynstunnelen_767x250.jpg

557 ms

reisepenger-autopafyll-banner-570x240.png

reisepenger-autopafyll-banner-570x240.png

690 ms

turist_banner_no.png

turist_banner_no.png

509 ms

ruter-logo.png

ruter-logo.png

225 ms

English.svg

English.svg

223 ms

load-spinner--dark-border.gif

load-spinner--dark-border.gif

250 ms

avvik_40x40_v2.svg

avvik_40x40_v2.svg

249 ms

kart_40x40_v2.svg

kart_40x40_v2.svg

224 ms

rutetabeller-linjekart_40x40_v2.svg

rutetabeller-linjekart_40x40_v2.svg

250 ms

reisegaranti-drosjerefusjon_40x40.svg

reisegaranti-drosjerefusjon_40x40.svg

252 ms

mobilbillett_40x40.svg

mobilbillett_40x40.svg

251 ms

reisekort_40x40.svg

reisekort_40x40.svg

250 ms

gtm.js

gtm.js

220 ms

DIN-Regular-webfont.woff

DIN-Regular-webfont.woff

111 ms

din-medium.woff

din-medium.woff

233 ms

DIN-Bold-webfont.woff

DIN-Bold-webfont.woff

110 ms

analytics.js

analytics.js

57 ms

linkid.js

linkid.js

11 ms

ec.js

ec.js

21 ms

collect

collect

12 ms

collect

collect

63 ms

bundle-print.css

bundle-print.css

126 ms

Accessibility Review

ruter.no accessibility score

85

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

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 IDs are not unique

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

ruter.no best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

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

ruter.no SEO score

92

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

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

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

ruter.no

Open Graph description is not detected on the main page of Ruter. 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: