Tools & Wizards About Us
agoda.no screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

agoda.no

Page Load Speed

5.5 sec in total

First Response

119 ms

Resources Loaded

5.3 sec

Page Rendered

52 ms

agoda.no screenshot

About Website

Welcome to agoda.no homepage info - get ready to check Agoda best content right away, or after learning these important things about agoda.no

Visit agoda.no

Key Findings

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

Performance Metrics

agoda.no performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value4,270 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

www.agoda.com

119 ms

6090-c486a3bd3c80.css

21 ms

home-94565aedfd91.css

58 ms

5993-b73e204fb80c.js

27 ms

3324-a96aa459e7ed.js

92 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Agoda.no, 21% (3 requests) were made to Cdn0.agoda.net and 14% (2 requests) were made to Agoda.com. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Cdn0.agoda.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (69%)

Content Size

4.7 MB

After Optimization

1.5 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Agoda.no main page is 4.7 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 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 146.7 kB

  • Original 200.4 kB
  • After minification 200.1 kB
  • After compression 53.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 146.7 kB or 73% of the original size.

JavaScript Optimization

-68%

Potential reduce by 2.7 MB

  • Original 4.0 MB
  • After minification 4.0 MB
  • After compression 1.3 MB

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 2.7 MB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 435.5 kB

  • Original 530.7 kB
  • After minification 530.3 kB
  • After compression 95.2 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. Agoda.no needs all CSS files to be minified and compressed as it can save up to 435.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (60%)

Requests Now

10

After Optimization

4

  • JavaScript
  • CSS

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

Network Requests Diagram

www.agoda.com

www.agoda.com

119 ms

6090-c486a3bd3c80.css

6090-c486a3bd3c80.css

21 ms

home-94565aedfd91.css

home-94565aedfd91.css

58 ms

5993-b73e204fb80c.js

5993-b73e204fb80c.js

27 ms

3324-a96aa459e7ed.js

3324-a96aa459e7ed.js

92 ms

6090-2fb73c105ab0.js

6090-2fb73c105ab0.js

53 ms

2206-963306516198.js

2206-963306516198.js

44 ms

home-82f44f62e285.js

home-82f44f62e285.js

44 ms

mcjs-worker.js

mcjs-worker.js

168 ms

134-a84cb98b362a.css

134-a84cb98b362a.css

150 ms

6270-48be7f01ed7b.js

6270-48be7f01ed7b.js

164 ms

Mallory-Book.woff

Mallory-Book.woff

4232 ms

mallory-light-webfont-v01.woff

mallory-light-webfont-v01.woff

4248 ms

mallory-medium.woff

mallory-medium.woff

4306 ms

Accessibility Review

agoda.no accessibility score

77

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

agoda.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

High

Missing source maps for large first-party JavaScript

SEO Factors

agoda.no SEO score

92

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Agoda.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 English. Our system also found out that Agoda.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

agoda.no

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