Tools & Wizards About Us
adatum.no screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

adatum.no

adatum - A blog about Azure, DevOps, Management, Automation and surrounding

Page Load Speed

3.8 sec in total

First Response

289 ms

Resources Loaded

2.9 sec

Page Rendered

577 ms

adatum.no screenshot

About Website

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

Adatum.no is a technical blog written by Microsoft Azure MVP, Martin Ehrnst. The blog focuses on Azure management, DevOps and Automation.

Visit adatum.no

Key Findings

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

adatum.no performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value530 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

adatum.no

289 ms

adatum.no

1594 ms

style.min.css

195 ms

mediaelementplayer-legacy.min.css

272 ms

wp-mediaelement.min.css

275 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 75% of them (40 requests) were addressed to the original Adatum.no, 11% (6 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Adatum.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.5 kB (20%)

Content Size

999.6 kB

After Optimization

804.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 100.1 kB

  • Original 125.5 kB
  • After minification 118.2 kB
  • After compression 25.4 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 100.1 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 1.6 kB

  • Original 239.9 kB
  • After minification 238.3 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. Adatum images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 383.6 kB
  • After minification 383.6 kB
  • After compression 381.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-37%

Potential reduce by 91.8 kB

  • Original 250.6 kB
  • After minification 250.4 kB
  • After compression 158.9 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. Adatum.no needs all CSS files to be minified and compressed as it can save up to 91.8 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (81%)

Requests Now

43

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

adatum.no

adatum.no

289 ms

adatum.no

adatum.no

1594 ms

style.min.css

style.min.css

195 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

272 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

275 ms

style-coblocks-1.css

style-coblocks-1.css

376 ms

style-coblocks-extensions.css

style-coblocks-extensions.css

286 ms

style-coblocks-animation.css

style-coblocks-animation.css

291 ms

style.min.css

style.min.css

293 ms

latest.css

latest.css

365 ms

bootstrap.min.css

bootstrap.min.css

460 ms

all.min.css

all.min.css

384 ms

css

css

36 ms

flexslider.css

flexslider.css

388 ms

style.css

style.css

392 ms

owl.carousel.min.css

owl.carousel.min.css

457 ms

owl.theme.default.css

owl.theme.default.css

469 ms

social-logos.min.css

social-logos.min.css

480 ms

jetpack.css

jetpack.css

582 ms

jquery.min.js

jquery.min.js

494 ms

jquery-migrate.min.js

jquery-migrate.min.js

549 ms

js

js

61 ms

adsbygoogle.js

adsbygoogle.js

119 ms

adsbygoogle.js

adsbygoogle.js

100 ms

gist-embed-6671625e2d3e.css

gist-embed-6671625e2d3e.css

28 ms

infinity.min.js

infinity.min.js

464 ms

coblocks-animation.js

coblocks-animation.js

474 ms

tiny-swiper.js

tiny-swiper.js

489 ms

coblocks-tinyswiper-initializer.js

coblocks-tinyswiper-initializer.js

604 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

604 ms

flexslider.min.js

flexslider.min.js

604 ms

owl.carousel.min.js

owl.carousel.min.js

604 ms

imagesloaded.min.js

imagesloaded.min.js

604 ms

shapely-scripts.js

shapely-scripts.js

605 ms

eu-cookie-law.min.js

eu-cookie-law.min.js

605 ms

e-202436.js

e-202436.js

23 ms

coblocks-gist-script.js

coblocks-gist-script.js

698 ms

sharing.min.js

sharing.min.js

698 ms

c1687b20-a085-4e74-b42c-8086ff5ee347-730x350.jpg

c1687b20-a085-4e74-b42c-8086ff5ee347-730x350.jpg

229 ms

Screenshot-2024-02-16-121524-1024x577.png

Screenshot-2024-02-16-121524-1024x577.png

383 ms

image-730x350.jpg

image-730x350.jpg

311 ms

microphone-640x350.jpg

microphone-640x350.jpg

155 ms

orange-small.png

orange-small.png

228 ms

MVP_Logo_Horizontal_Preferred_Cyan300_CMYK_72ppi1.png

MVP_Logo_Horizontal_Preferred_Cyan300_CMYK_72ppi1.png

228 ms

show_ads_impl.js

show_ads_impl.js

399 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

76 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

137 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

157 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

158 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

159 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

158 ms

fa-solid-900.woff

fa-solid-900.woff

232 ms

fa-regular-400.woff

fa-regular-400.woff

265 ms

Accessibility Review

adatum.no accessibility score

88

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

Links do not have a discernible name

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.

Best Practices

adatum.no best practices score

92

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

Page has valid source maps

SEO Factors

adatum.no SEO score

97

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Adatum.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Adatum.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

adatum.no

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