Tools & Wizards About Us
orkide.no screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

orkide.no

OrkideEkspressen | Spesialisten på eksotiske reiser

Page Load Speed

5.2 sec in total

First Response

682 ms

Resources Loaded

4 sec

Page Rendered

508 ms

orkide.no screenshot

About Website

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

Skreddersydde reiser til Thailand, Bali, Japan og andre eksotiske reisemål. Erfarne reiserådgivere hjelper deg å planlegge reisen.

Visit orkide.no

Key Findings

We analyzed Orkide.no page load time and found that the first response time was 682 ms and then it took 4.5 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

orkide.no performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

www.orkide.no

682 ms

gtm.js

78 ms

cookieblocker.min.css

102 ms

pagenavi-css.css

273 ms

slick.css

366 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 74% of them (56 requests) were addressed to the original Orkide.no, 8% (6 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Orkide.matomo.cloud. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Orkide.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.3 kB (3%)

Content Size

6.0 MB

After Optimization

5.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Orkide.no main page is 6.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. 60% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 60.9 kB

  • Original 72.8 kB
  • After minification 59.4 kB
  • After compression 12.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 13.4 kB, which is 18% 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 60.9 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 54.8 kB

  • Original 5.8 MB
  • After minification 5.7 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. Orkide images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 39.7 kB

  • Original 136.1 kB
  • After minification 136.1 kB
  • After compression 96.4 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 39.7 kB or 29% of the original size.

CSS Optimization

-42%

Potential reduce by 11.9 kB

  • Original 28.2 kB
  • After minification 28.2 kB
  • After compression 16.3 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. Orkide.no needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (49%)

Requests Now

68

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.orkide.no

www.orkide.no

682 ms

gtm.js

gtm.js

78 ms

cookieblocker.min.css

cookieblocker.min.css

102 ms

pagenavi-css.css

pagenavi-css.css

273 ms

slick.css

slick.css

366 ms

style.css

style.css

477 ms

slick.css

slick.css

367 ms

slick-theme.css

slick-theme.css

366 ms

css2

css2

36 ms

jquery.min.js

jquery.min.js

489 ms

jquery-migrate.min.js

jquery-migrate.min.js

373 ms

script.js

script.js

457 ms

custom-accordion.js

custom-accordion.js

457 ms

mobile.js

mobile.js

459 ms

slick.min.js

slick.min.js

487 ms

slick.js

slick.js

588 ms

banner-slider.js

banner-slider.js

552 ms

acf-google-maps.js

acf-google-maps.js

551 ms

complianz.min.js

complianz.min.js

591 ms

forms.js

forms.js

588 ms

js

js

46 ms

analytics.js

analytics.js

18 ms

collect

collect

116 ms

collect

collect

49 ms

ga-audiences

ga-audiences

35 ms

9-Beach-Large-560x300.jpg

9-Beach-Large-560x300.jpg

168 ms

Titicaca4-Large-560x300.jpeg

Titicaca4-Large-560x300.jpeg

295 ms

IMG12-Anse-Lazio-secondary-Beach-2-Large-560x300.jpg

IMG12-Anse-Lazio-secondary-Beach-2-Large-560x300.jpg

316 ms

HH031-Aerial-View-of-Pools2-560x300.jpg

HH031-Aerial-View-of-Pools2-560x300.jpg

302 ms

finndinreise.svg

finndinreise.svg

196 ms

snakkmedoss.svg

snakkmedoss.svg

198 ms

forslag.svg

forslag.svg

255 ms

tilpass.svg

tilpass.svg

269 ms

pakkkofferten.svg

pakkkofferten.svg

271 ms

shutterstock_733267456-Large-560x300.jpg

shutterstock_733267456-Large-560x300.jpg

381 ms

shutterstock_4347204822-560x300.jpg

shutterstock_4347204822-560x300.jpg

444 ms

facebook-square-brands.svg

facebook-square-brands.svg

362 ms

instagram-brands.svg

instagram-brands.svg

386 ms

Artboard_1.svg

Artboard_1.svg

383 ms

search.svg

search.svg

395 ms

STB-19-Grand-Anse-La-Digue-2-Large.jpg

STB-19-Grand-Anse-La-Digue-2-Large.jpg

1535 ms

arrow-right2.svg

arrow-right2.svg

462 ms

Cha-Am1-2.jpeg

Cha-Am1-2.jpeg

1779 ms

Sugar_Beach_Aerial_View_17-2-Large.jpg

Sugar_Beach_Aerial_View_17-2-Large.jpg

818 ms

Machu-Picchu-Large.jpeg

Machu-Picchu-Large.jpeg

1272 ms

AdobeStock_87545362-Large.jpeg

AdobeStock_87545362-Large.jpeg

1111 ms

shutterstock_330162092-Large.jpg

shutterstock_330162092-Large.jpg

1330 ms

gruppereiser.svg

gruppereiser.svg

911 ms

sologbad.svg

sologbad.svg

1003 ms

familiereiser.svg

familiereiser.svg

1096 ms

opplevelsesreiser.svg

opplevelsesreiser.svg

1187 ms

IMG_0736-2-scaled.jpg

IMG_0736-2-scaled.jpg

1889 ms

Vespatur-3-Medium.jpg

Vespatur-3-Medium.jpg

1287 ms

IMG_0534-Large.jpg

IMG_0534-Large.jpg

2008 ms

Japan-2-3-Large.jpg

Japan-2-3-Large.jpg

1396 ms

20190103_122031-2-Large.jpg

20190103_122031-2-Large.jpg

2383 ms

matomo.js

matomo.js

130 ms

matomo.js

matomo.js

130 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPw.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPw.ttf

22 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkA.ttf

38 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_AkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_AkA.ttf

54 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkA.ttf

53 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkA.ttf

53 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkA.ttf

54 ms

bounce

bounce

9 ms

IMG_99545-Large.jpg

IMG_99545-Large.jpg

1480 ms

ajax-loader.gif

ajax-loader.gif

1457 ms

chevron-thin-left.svg

chevron-thin-left.svg

1476 ms

chevron-thin-right.svg

chevron-thin-right.svg

1549 ms

chevron-thin-left-black.svg

chevron-thin-left-black.svg

1569 ms

chevron-thin-right-black.svg

chevron-thin-right-black.svg

1638 ms

matomo.php

matomo.php

458 ms

slick.woff

slick.woff

1629 ms

configs.php

configs.php

380 ms

configs.php

configs.php

380 ms

matomo.php

matomo.php

150 ms

Accessibility Review

orkide.no accessibility score

99

Accessibility Issues

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

orkide.no best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

orkide.no SEO score

98

Search Engine Optimization Advices

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

    NB

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orkide.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 Orkide.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

orkide.no

Open Graph data is detected on the main page of Orkide. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: