5 sec in total
540 ms
4.2 sec
216 ms
Welcome to nettbuss.no homepage info - get ready to check Nettbuss best content for Norway right away, or after learning these important things about nettbuss.no
Vybuss.no. Her kjøper du billetter til alle bussavganger med Vy Buss. Du finner også informasjon om rutetider, trafikkstatus, avbestilling og hittegods.
Visit nettbuss.noWe analyzed Nettbuss.no page load time and found that the first response time was 540 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
nettbuss.no performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value15.2 s
0/100
25%
Value6.8 s
35/100
10%
Value1,140 ms
22/100
30%
Value0.015
100/100
15%
Value17.9 s
3/100
10%
540 ms
1612 ms
623 ms
67 ms
1077 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 87% of them (76 requests) were addressed to the original Nettbuss.no, 5% (4 requests) were made to Maps.googleapis.com and 3% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Nettbuss.no.
Page size can be reduced by 1.0 MB (52%)
2.0 MB
979.6 kB
In fact, the total size of Nettbuss.no main page is 2.0 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. 55% of websites need less resources to load. Javascripts take 943.5 kB which makes up the majority of the site volume.
Potential reduce by 171.7 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 171.7 kB or 80% of the original size.
Potential reduce by 49.7 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. Nettbuss images are well optimized though.
Potential reduce by 655.8 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 655.8 kB or 70% of the original size.
Potential reduce by 166.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. Nettbuss.no needs all CSS files to be minified and compressed as it can save up to 166.6 kB or 87% of the original size.
Number of requests can be reduced by 45 (53%)
85
40
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nettbuss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.
nettbuss.no
540 ms
www.nettbuss.no
1612 ms
styles.css
623 ms
js
67 ms
WebPublisher.Modules.TravelBooking.min.js
1077 ms
jquery-ui.css
396 ms
Helpers.js
287 ms
CoreFunctionsPublic.js
540 ms
jquery.stickyPanel.min.js
504 ms
CalendarPopup.min.js
434 ms
jquery.caret.min.js
540 ms
slides.min.jquery.js
668 ms
Step1_2.js
693 ms
Login_2.js
654 ms
html5.js
652 ms
PopupView.js
677 ms
GoogleMarkerWithLabelV3.js
770 ms
InfoBoxHandler.js
779 ms
ShowStopsOnMap.js
791 ms
jquery.scroll.js
803 ms
jquery.switch.js
831 ms
FindYourStop.js
894 ms
markerclustererplus.js
1020 ms
UserGeoLocation.js
915 ms
ga.js
48 ms
common.js
23 ms
util.js
43 ms
marker.js
24 ms
Google_Translate_logo.png
149 ms
56531bdc6a5bd4b17cc9210fd9633fa4.png
148 ms
9ee70b7987a735c046ac30a1556272c8.png
150 ms
2c41848295efeeb47beabefb10751ed3.png
149 ms
1138d90ef0a0848a542e57d1595f58ea.png
150 ms
13128f39fb3e7f95638f40923a83d453.jpg
461 ms
194c809b99ee613b8f5f2b85fc79f7e4.jpg
382 ms
c8135a3d116eed9c0879146634b2dd57.jpg
273 ms
be04b1ed09ed7d60b621315071c300cd.jpg
294 ms
9d5ce379163bb569eaec48e30ee1bf3f.jpg
275 ms
b433207eef28242a9952273cd6bed782.jpg
382 ms
getfile.aspx
501 ms
46d1980e375ce08915b30d9a328c2fdc.jpg
587 ms
9c72e0c8882794b79d65f14776a0a974.png
491 ms
b8599b9343f82e3bc30984ca4f3fea3f.png
521 ms
e8432fb72c61c9066957124e5a420a05.png
504 ms
a6d5ab67798f3a675dc50c1d5b6c03d4.png
674 ms
nettbussno-logo.svg
641 ms
icon_globe.png
630 ms
icon_user.png
652 ms
icon_login.png
666 ms
bk_menu.png
719 ms
bk_minigrad.png
748 ms
icon_search_dark.png
753 ms
bk_grad.png
765 ms
warning.png
836 ms
bk_grad_select.png
841 ms
shadow_box.png
846 ms
inputoverlay_location_inactive_large.png
869 ms
btn_switch.png
868 ms
icon_cal.png
867 ms
icon_clock2.png
961 ms
__utm.gif
15 ms
icon_right.png
928 ms
arrow_big.png
949 ms
bk_info.png
956 ms
icon_info_big.png
957 ms
addthis_widget.js
15 ms
arrow_small.png
897 ms
bk_info_bottom.png
968 ms
icon_tlf.png
968 ms
icon_warn.png
995 ms
icon_ticket.png
998 ms
GetLanguages
901 ms
icon_brief.png
886 ms
icon_service.png
971 ms
shadow_article.png
876 ms
tagline.png
895 ms
btn_search_dark.png
814 ms
ui-bg_inset-hard_100_ffffff_1x100.png
795 ms
ui-bg_flat_0_0098db_40x100.png
807 ms
ui-bg_glass_45_f0f0f0_1x400.png
880 ms
ui-bg_flat_50_0098db_40x100.png
876 ms
13128f39fb3e7f95638f40923a83d453.jpg
927 ms
loader_FFF_666.gif
771 ms
300lo.json
23 ms
counter.8eb9e83b9fa0d4af1e4f.js
6 ms
sh.7c7179124ea24ac6ba46caac.html
39 ms
shares.json
32 ms
nettbuss.no accessibility score
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
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
nettbuss.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
nettbuss.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NO
NB
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nettbuss.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 language. Our system also found out that Nettbuss.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.
nettbuss.no
Open Graph description is not detected on the main page of Nettbuss. 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: