Tools & Wizards About Us
onnibus.fi screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

onnibus.fi

Bussilippukauppa - Halpoja bussilippuja tuhansille pysäkeille - OnniBus on Suomen iloisin ja tunnetuin bussiyhtiö - OnniBus

Page Load Speed

3.1 sec in total

First Response

331 ms

Resources Loaded

2.6 sec

Page Rendered

197 ms

onnibus.fi screenshot

About Website

Welcome to onnibus.fi homepage info - get ready to check Onni Bus best content right away, or after learning these important things about onnibus.fi

Suomen iloisin ja edullisin bussilippukauppa! Varaa matkaliput verkkokaupasta nopeasti ja jopa 1 eurolla! Lukuisia tarjouksia. Matkusta halvalla ja luotettavasti OnniBus MEGA, OnniBus FLEX ja muiden y...

Visit onnibus.fi

Key Findings

We analyzed Onnibus.fi page load time and found that the first response time was 331 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

onnibus.fi performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value12,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.641

9/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

onnibus.fi

331 ms

www.onnibus.com

243 ms

index.htm

195 ms

bootstrap.min.css

435 ms

onnibus-styles.css

458 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Onnibus.fi, 50% (32 requests) were made to Onnibus.com and 20% (13 requests) were made to Booking.onnibus.com. The less responsive or slowest element that took the longest time to load (747 ms) relates to the external source Onnibus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 868.9 kB (41%)

Content Size

2.1 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onnibus.fi main page is 2.1 MB. 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. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 22.9 kB

  • Original 29.8 kB
  • After minification 26.2 kB
  • After compression 6.9 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.6 kB, which is 12% 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 22.9 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 129.3 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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, Onni Bus needs image optimization as it can save up to 129.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 309.3 kB

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

CSS Optimization

-87%

Potential reduce by 407.4 kB

  • Original 467.4 kB
  • After minification 367.0 kB
  • After compression 60.1 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. Onnibus.fi needs all CSS files to be minified and compressed as it can save up to 407.4 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

49

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onnibus.fi

onnibus.fi

331 ms

www.onnibus.com

www.onnibus.com

243 ms

index.htm

index.htm

195 ms

bootstrap.min.css

bootstrap.min.css

435 ms

onnibus-styles.css

onnibus-styles.css

458 ms

jquery.min.js

jquery.min.js

488 ms

bootstrap.min.js

bootstrap.min.js

279 ms

expand-seating-plan.js

expand-seating-plan.js

99 ms

bootstrap-popovers-seating-plan.js

bootstrap-popovers-seating-plan.js

190 ms

livestagetest.js

livestagetest.js

193 ms

analytics.js

analytics.js

115 ms

cse.js

cse.js

113 ms

Selections

Selections

632 ms

topBG.jpg

topBG.jpg

108 ms

top2.png

top2.png

106 ms

Onnibus-Logo-L.svg

Onnibus-Logo-L.svg

107 ms

souter-flag-sprite.png

souter-flag-sprite.png

93 ms

01_ONNIhome-crls-FI.jpg

01_ONNIhome-crls-FI.jpg

549 ms

02_ONNIhome-crls-FI.jpg

02_ONNIhome-crls-FI.jpg

680 ms

03_ONNIhome-crls-FI.jpg

03_ONNIhome-crls-FI.jpg

747 ms

04_ONNIhome-crls-FI.jpg

04_ONNIhome-crls-FI.jpg

667 ms

onb_SM-map-finland.jpg

onb_SM-map-finland.jpg

199 ms

white.png

white.png

198 ms

Onnibus-Logo-S.svg

Onnibus-Logo-S.svg

315 ms

secure.png

secure.png

314 ms

mana-footer.png

mana-footer.png

411 ms

polski-footer.png

polski-footer.png

411 ms

polskiGOLD-footer.png

polskiGOLD-footer.png

496 ms

super-footer.png

super-footer.png

494 ms

klaklak-footer.png

klaklak-footer.png

589 ms

entee-footer.png

entee-footer.png

590 ms

cse.js

cse.js

97 ms

muli.woff

muli.woff

541 ms

FredokaOne-Regular.woff

FredokaOne-Regular.woff

615 ms

montserrat-regular.woff

montserrat-regular.woff

602 ms

montserrat-bold.woff

montserrat-bold.woff

653 ms

onb_font_1.woff

onb_font_1.woff

666 ms

linkid.js

linkid.js

21 ms

ecommerce.js

ecommerce.js

27 ms

collect

collect

53 ms

collect

collect

10 ms

jsapi

jsapi

44 ms

default+fi.css

default+fi.css

11 ms

default.css

default.css

25 ms

default+fi.I.js

default+fi.I.js

27 ms

default.css

default.css

39 ms

async-ads.js

async-ads.js

137 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

76 ms

small-logo.png

small-logo.png

18 ms

search_box_icon.png

search_box_icon.png

41 ms

clear.png

clear.png

15 ms

bootstrap.min.css

bootstrap.min.css

457 ms

onnibus-engine.css

onnibus-engine.css

279 ms

jquery1.11.0.min.js

jquery1.11.0.min.js

507 ms

jquery-ui-1.10.4.custom.min.js

jquery-ui-1.10.4.custom.min.js

566 ms

jquery.ui.datepicker-fi.js

jquery.ui.datepicker-fi.js

192 ms

site.js

site.js

299 ms

bootstrap.min.js

bootstrap.min.js

304 ms

collect

collect

9 ms

muli.woff

muli.woff

103 ms

onb_font_1.woff

onb_font_1.woff

285 ms

montserrat-regular.woff

montserrat-regular.woff

102 ms

montserrat-bold.woff

montserrat-bold.woff

119 ms

FredokaOne-Regular.woff

FredokaOne-Regular.woff

91 ms

Accessibility Review

onnibus.fi accessibility score

98

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

onnibus.fi 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

onnibus.fi SEO score

90

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

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

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

onnibus.fi

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