Tools & Wizards About Us
wideroe.no screenshot

Report Summary

  • 0

    Performance

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

wideroe.no

Bestill flybilletter | Widerøe

Page Load Speed

3.6 sec in total

First Response

308 ms

Resources Loaded

3.1 sec

Page Rendered

164 ms

wideroe.no screenshot

About Website

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

Bestill flybilletter med Widerøe. Vi flyr deg til 42 destinasjoner i Norge og 8 destinasjoner i utlandet. Bestill din flyreise nå.

Visit wideroe.no

Key Findings

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

Performance Metrics

wideroe.no performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

wideroe.no

308 ms

www.wideroe.no

1284 ms

fontface.css

205 ms

screen.css

308 ms

wf.css

303 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 68% of them (74 requests) were addressed to the original Wideroe.no, 6% (6 requests) were made to Google.com and 3% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Wideroe.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 700.8 kB (58%)

Content Size

1.2 MB

After Optimization

503.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wideroe.no main page is 1.2 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 655.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 113.3 kB

  • Original 141.3 kB
  • After minification 121.9 kB
  • After compression 28.0 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 19.4 kB, which is 14% 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 113.3 kB or 80% of the original size.

Image Optimization

-21%

Potential reduce by 52.2 kB

  • Original 252.3 kB
  • After minification 200.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, Wideroe needs image optimization as it can save up to 52.2 kB or 21% 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 403.0 kB

  • Original 655.6 kB
  • After minification 542.7 kB
  • After compression 252.6 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 403.0 kB or 61% of the original size.

CSS Optimization

-86%

Potential reduce by 132.4 kB

  • Original 154.6 kB
  • After minification 104.4 kB
  • After compression 22.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. Wideroe.no needs all CSS files to be minified and compressed as it can save up to 132.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (59%)

Requests Now

99

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wideroe.no

wideroe.no

308 ms

www.wideroe.no

www.wideroe.no

1284 ms

fontface.css

fontface.css

205 ms

screen.css

screen.css

308 ms

wf.css

wf.css

303 ms

responsive.css

responsive.css

314 ms

wffrontpage.css

wffrontpage.css

210 ms

modernizr.custom.39113.js

modernizr.custom.39113.js

305 ms

jquery.min.js

jquery.min.js

32 ms

jquery-ui-1.8.18.custom.min.js

jquery-ui-1.8.18.custom.min.js

624 ms

jquery.ui.selectmenu.js

jquery.ui.selectmenu.js

401 ms

jquery.ui.custominput.js

jquery.ui.custominput.js

402 ms

wfbook_utils.js

wfbook_utils.js

403 ms

wfbook_rules.js

wfbook_rules.js

406 ms

wfstrings.js

wfstrings.js

524 ms

wfscripts.js

wfscripts.js

523 ms

routemap.js

routemap.js

522 ms

jquery.responsiveWeb.js

jquery.responsiveWeb.js

522 ms

responsive.js

responsive.js

521 ms

jquery.ui.datepicker-no.js

jquery.ui.datepicker-no.js

644 ms

jquery.ui.datepicker-en-GB.js

jquery.ui.datepicker-en-GB.js

644 ms

wfbook_citylogic.js

wfbook_citylogic.js

642 ms

bf1.js

bf1.js

643 ms

responsive.css

responsive.css

641 ms

_11_zone.js

_11_zone.js

722 ms

swfobject.js

swfobject.js

718 ms

_11_zone.css

_11_zone.css

732 ms

11_zone.css

11_zone.css

720 ms

jsapi

jsapi

18 ms

bg.png

bg.png

401 ms

430 ms

Z4DRkrGYCGHyQfUtXktw2Ma5vRaDFxju-min.js

Z4DRkrGYCGHyQfUtXktw2Ma5vRaDFxju-min.js

531 ms

WebResource.axd

WebResource.axd

341 ms

fbds.js

fbds.js

6 ms

104 ms

no_big.png

no_big.png

105 ms

arrowDown.png

arrowDown.png

108 ms

no.png

no.png

102 ms

uk.png

uk.png

105 ms

logo.png

logo.png

104 ms

input-search-light_grey.png

input-search-light_grey.png

108 ms

ShowImageCMImage.ashx

ShowImageCMImage.ashx

291 ms

ShowImageCMImage.ashx

ShowImageCMImage.ashx

292 ms

ShowImageCMImage.ashx

ShowImageCMImage.ashx

290 ms

rm_no.jpg

rm_no.jpg

201 ms

berit_jq.png

berit_jq.png

204 ms

egil_jq.png

egil_jq.png

210 ms

frank_jq.png

frank_jq.png

308 ms

gerdanne_jq.png

gerdanne_jq.png

306 ms

hanspetter_jq.png

hanspetter_jq.png

313 ms

kjetil_jq.png

kjetil_jq.png

391 ms

linda_jq.png

linda_jq.png

390 ms

maybritt_jq.png

maybritt_jq.png

392 ms

merete_jq.png

merete_jq.png

409 ms

merethe_jq.png

merethe_jq.png

414 ms

odd_jq.png

odd_jq.png

416 ms

tove_jq.png

tove_jq.png

653 ms

trondare_jq.png

trondare_jq.png

653 ms

vidar_jq.png

vidar_jq.png

654 ms

tom_jq.png

tom_jq.png

653 ms

13 ms

default+no.I.js

default+no.I.js

8 ms

body-bg.png

body-bg.png

595 ms

input-date.png

input-date.png

594 ms

routemap-map.png

routemap-map.png

650 ms

plane.png

plane.png

596 ms

me.png

me.png

597 ms

hotel.png

hotel.png

596 ms

car.png

car.png

597 ms

blank.png

blank.png

583 ms

google.png

google.png

643 ms

facebook.png

facebook.png

643 ms

twitter.png

twitter.png

648 ms

bind

bind

366 ms

ScalaSansWebPro-bold.woff

ScalaSansWebPro-bold.woff

650 ms

ScalaSansWebPro.woff

ScalaSansWebPro.woff

751 ms

youtubeButton.png

youtubeButton.png

703 ms

2a325fc7aecd.png

2a325fc7aecd.png

10 ms

212 ms

cx.js

cx.js

179 ms

gtm.js

gtm.js

182 ms

b6505e3f-550f-4a93-ae48-08eff84a9102.js

b6505e3f-550f-4a93-ae48-08eff84a9102.js

175 ms

async-ads.js

async-ads.js

65 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

31 ms

input-radio-checked.png

input-radio-checked.png

174 ms

input-radio.png

input-radio.png

170 ms

input-selector.png

input-selector.png

188 ms

input-selector-blue.png

input-selector-blue.png

198 ms

datepicker-next.png

datepicker-next.png

243 ms

datepicker-prev.png

datepicker-prev.png

271 ms

small-logo.png

small-logo.png

33 ms

boxever-min.js

boxever-min.js

160 ms

Pong.ashx

Pong.ashx

74 ms

dc.js

dc.js

42 ms

fbevents.js

fbevents.js

28 ms

54651.js

54651.js

278 ms

target

target

67 ms

36 ms

p1.html

p1.html

9 ms

38 ms

31 ms

p1.js

p1.js

28 ms

inpage_linkid.js

inpage_linkid.js

32 ms

inv.gif

inv.gif

11 ms

rep.gif

rep.gif

11 ms

__utm.gif

__utm.gif

11 ms

__utm.gif

__utm.gif

12 ms

create.json

create.json

140 ms

rwa.js

rwa.js

160 ms

Accessibility Review

wideroe.no accessibility score

69

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

Document doesn't have a <title> element

High

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

wideroe.no best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

wideroe.no SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wideroe.no can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Norwegian. Our system also found out that Wideroe.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

wideroe.no

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