Tools & Wizards About Us
tbanen.no screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

tbanen.no

Sporveien AS - Velkommen til Sporveien, Norges største leverandør av kollektivtrafikk

Page Load Speed

5.9 sec in total

First Response

1 sec

Resources Loaded

4.5 sec

Page Rendered

355 ms

tbanen.no screenshot

About Website

Visit tbanen.no now to see the best up-to-date Tbanen content and also check out these interesting facts you probably never knew about tbanen.no

Velkommen til Sporveien, Norges største leverandør av kollektivtrafikk.

Visit tbanen.no

Key Findings

We analyzed Tbanen.no page load time and found that the first response time was 1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

tbanen.no performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

www.tbanen.no

1023 ms

iknowbase.css

204 ms

iknowbase-and-jquery-min.js

409 ms

iknowbase-common-full-min.js

320 ms

css

76 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 35% of them (29 requests) were addressed to the original Tbanen.no, 39% (32 requests) were made to Ruter.no and 12% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Tbanen.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 612.8 kB (78%)

Content Size

785.6 kB

After Optimization

172.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tbanen.no main page is 785.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. 60% of websites need less resources to load. CSS take 390.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 47.1 kB

  • Original 58.0 kB
  • After minification 49.3 kB
  • After compression 10.8 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 8.6 kB, which is 15% 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 47.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 877 B
  • After minification 877 B

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. Tbanen images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 237.3 kB

  • Original 335.8 kB
  • After minification 270.6 kB
  • After compression 98.5 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 237.3 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 328.4 kB

  • Original 390.9 kB
  • After minification 332.4 kB
  • After compression 62.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. Tbanen.no needs all CSS files to be minified and compressed as it can save up to 328.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (62%)

Requests Now

69

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tbanen.no

www.tbanen.no

1023 ms

iknowbase.css

iknowbase.css

204 ms

iknowbase-and-jquery-min.js

iknowbase-and-jquery-min.js

409 ms

iknowbase-common-full-min.js

iknowbase-common-full-min.js

320 ms

css

css

76 ms

bootstrap.min.css

bootstrap.min.css

429 ms

twitterFetcher_v10_min.js

twitterFetcher_v10_min.js

204 ms

bootstrap.min.js

bootstrap.min.js

210 ms

bootstrap-carousel.js

bootstrap-carousel.js

199 ms

ktpas_utils_v1.1.js

ktpas_utils_v1.1.js

210 ms

tbanen_custom.css

tbanen_custom.css

214 ms

sdk.js

sdk.js

209 ms

logo_header_tbanen.svg

logo_header_tbanen.svg

175 ms

logo_header_trikken.svg

logo_header_trikken.svg

176 ms

logo_header_sporveien.svg

logo_header_sporveien.svg

167 ms

tbane_rutetabell.jpg

tbane_rutetabell.jpg

188 ms

sporveien_briefcase.svg

sporveien_briefcase.svg

181 ms

iframe-search.html

iframe-search.html

1035 ms

logo_standalone.svg

logo_standalone.svg

144 ms

Forslag%203.jpg

Forslag%203.jpg

1238 ms

20150929_104752.jpg

20150929_104752.jpg

1015 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

680 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

773 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

707 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

707 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

708 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

705 ms

Klavika-Regular.otf

Klavika-Regular.otf

744 ms

PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff

PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff

581 ms

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

580 ms

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

645 ms

PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff

PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff

583 ms

PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff

PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff

582 ms

426312021303250945

426312021303250945

562 ms

700 ms

xd_arbiter.php

xd_arbiter.php

564 ms

xd_arbiter.php

xd_arbiter.php

690 ms

logo_footer_cropped.svg

logo_footer_cropped.svg

519 ms

icon-trikk.svg

icon-trikk.svg

521 ms

icon-tbane.svg

icon-tbane.svg

537 ms

social-fb.svg

social-fb.svg

616 ms

social-twitter.svg

social-twitter.svg

615 ms

social-instagram.svg

social-instagram.svg

638 ms

social-linkedin.svg

social-linkedin.svg

699 ms

social-youtube.svg

social-youtube.svg

706 ms

ga.js

ga.js

411 ms

jquery.cluetip.css

jquery.cluetip.css

673 ms

__utm.gif

__utm.gif

18 ms

iframe-search.html

iframe-search.html

565 ms

jquery.min.js

jquery.min.js

28 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

108 ms

jquery-ui.min.js

jquery-ui.min.js

45 ms

jquery-ui.css

jquery-ui.css

45 ms

jqtransform.js

jqtransform.js

215 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

295 ms

jquery.autocomplete.js

jquery.autocomplete.js

324 ms

jquery.ruter.autocomplete.js

jquery.ruter.autocomplete.js

321 ms

ruter.js

ruter.js

423 ms

jq_autocomplete.css

jq_autocomplete.css

325 ms

jq_transform.css

jq_transform.css

321 ms

reset.css

reset.css

392 ms

c_grid.css

c_grid.css

448 ms

components.css

components.css

439 ms

styles.css

styles.css

426 ms

responsive.css

responsive.css

448 ms

retina.css

retina.css

490 ms

modernizr.js

modernizr.js

524 ms

init.js

init.js

520 ms

c_base.css

c_base.css

106 ms

c_text.css

c_text.css

109 ms

c_footer.css

c_footer.css

106 ms

c_accordion.css

c_accordion.css

150 ms

c_arrows.css

c_arrows.css

179 ms

c_buttons.css

c_buttons.css

185 ms

c_boxes.css

c_boxes.css

211 ms

c_forms.css

c_forms.css

208 ms

c_tabs.css

c_tabs.css

209 ms

c_lightbox.css

c_lightbox.css

245 ms

c_icons.css

c_icons.css

275 ms

main_bg.png

main_bg.png

109 ms

search-light-logo.png

search-light-logo.png

110 ms

din-bold-webfont.woff

din-bold-webfont.woff

106 ms

print.css

print.css

108 ms

Accessibility Review

tbanen.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

High

<frame> or <iframe> elements do not have a title

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

tbanen.no 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

tbanen.no SEO score

83

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

High

Page is blocked from indexing

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

    NO

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

tbanen.no

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