2 sec in total
31 ms
1.7 sec
185 ms
Visit viatravel.no now to see the best up-to-date Viatravel content for Norway and also check out these interesting facts you probably never knew about viatravel.no
Finn løsninger for forretningsreiseadministrasjon som passer både store og små bedrifter. Egencia gjør forretningsreiser enklere – og bedre.
Visit viatravel.noWe analyzed Viatravel.no page load time and found that the first response time was 31 ms and then it took 1.9 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.
viatravel.no performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value9.7 s
0/100
25%
Value6.9 s
34/100
10%
Value4,410 ms
1/100
30%
Value0.003
100/100
15%
Value17.3 s
4/100
10%
31 ms
315 ms
170 ms
46 ms
270 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Viatravel.no, 54% (26 requests) were made to Egencia.no and 8% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (751 ms) relates to the external source Egencia.no.
Page size can be reduced by 572.7 kB (53%)
1.1 MB
501.1 kB
In fact, the total size of Viatravel.no main page is 1.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. 50% of websites need less resources to load. Javascripts take 423.7 kB which makes up the majority of the site volume.
Potential reduce by 29.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 6.1 kB, which is 16% 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 29.8 kB or 78% of the original size.
Potential reduce by 634 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. Viatravel images are well optimized though.
Potential reduce by 287.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 287.2 kB or 68% of the original size.
Potential reduce by 255.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. Viatravel.no needs all CSS files to be minified and compressed as it can save up to 255.1 kB or 88% of the original size.
Number of requests can be reduced by 18 (46%)
39
21
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viatravel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
viatravel.no
31 ms
www.egencia.no
315 ms
170 ms
fonts.css
46 ms
flexslider.css
270 ms
egencia.css
17 ms
379b56821c34.js
357 ms
5c5d9d3ffaccefe7b30f3ad077147478.jpg
23 ms
010dc12fe20bc9242e617c652229f1d7.jpg
176 ms
846fc9979288ad1606fd04f7aa55ae98.jpg
135 ms
6d8549397c67eda6a560ec410c3577ad.jpg
20 ms
8c6625dea155432b56f65a4e11edba80.jpg
20 ms
b05fd5f7d50c60697a3e539df6877d34.jpg
20 ms
d81556b495b94c1ef3fa356296acc907.jpg
22 ms
4d188435ada8d6d958111c30e0982a62.jpg
21 ms
5441b1d99627ef171248ddb7372edaec.jpg
24 ms
gtm.js
22 ms
egencia.svg
161 ms
egencia.png
64 ms
egencia_sprites.png
200 ms
analytics.js
31 ms
conversion_async.js
36 ms
iframe_api
64 ms
w.js
29 ms
fbevents.js
28 ms
munchkin-beta.js
46 ms
Urbano-Regular-webfont.ttf
153 ms
egenciaicons-regular-webfont.ttf
751 ms
linkid.js
23 ms
clickstream.min.js
116 ms
165 ms
178 ms
munchkin.js
116 ms
no.png
158 ms
a1dc4d80626893ab517874c4e08600a7.jpg
248 ms
5e6f51472ef203ca927e3105903418b3.jpg
187 ms
6de4cc7bfbd390da02e915f62a81ab54.jpg
222 ms
baa789e323d7ba7a7ebf5d2a0d1e51ba.jpg
189 ms
www-widgetapi.js
75 ms
collect
27 ms
collect
95 ms
Urbano-Bold-webfont.ttf
361 ms
storage.luckyorange.net
81 ms
visitWebPage
168 ms
29 ms
ga-audiences
21 ms
settings.luckyorange.net
11 ms
collect
2 ms
viatravel.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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
viatravel.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
viatravel.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Viatravel.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 Viatravel.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.
viatravel.no
Open Graph description is not detected on the main page of Viatravel. 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: