2.2 sec in total
277 ms
1.6 sec
319 ms
Visit edr.no now to see the best up-to-date Edr content and also check out these interesting facts you probably never knew about edr.no
Visit edr.noWe analyzed Edr.no page load time and found that the first response time was 277 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.
edr.no performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.2 s
73/100
25%
Value2.8 s
96/100
10%
Value90 ms
98/100
30%
Value0.242
51/100
15%
Value3.1 s
95/100
10%
277 ms
579 ms
154 ms
174 ms
248 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Edr.no, 83% (25 requests) were made to Edrmedeso.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (580 ms) relates to the external source Edrmedeso.com.
Page size can be reduced by 418.8 kB (48%)
869.8 kB
451.0 kB
In fact, the total size of Edr.no main page is 869.8 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. 40% of websites need less resources to load. Javascripts take 339.2 kB which makes up the majority of the site volume.
Potential reduce by 77.3 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 16.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 77.3 kB or 86% of the original size.
Potential reduce by 23.6 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. Edr images are well optimized though.
Potential reduce by 204.8 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 204.8 kB or 60% of the original size.
Potential reduce by 113.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. Edr.no needs all CSS files to be minified and compressed as it can save up to 113.1 kB or 83% of the original size.
Number of requests can be reduced by 11 (48%)
23
12
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
edr.no
277 ms
edrmedeso.com
579 ms
language-selector.css
154 ms
main.css
174 ms
main.min.css
248 ms
scripts.min.js
173 ms
jquery.min.js
30 ms
wp-emoji-release.min.js
199 ms
modernizr.min.js
139 ms
scripts.min.js
233 ms
wp-embed.min.js
139 ms
sitepress.js
139 ms
js_composer_front.min.js
140 ms
jquery.json.js
179 ms
gravityforms.min.js
189 ms
placeholders.jquery.min.js
183 ms
analytics.js
103 ms
retina_logo.png
105 ms
graphic-two.png
580 ms
footer_form.jpg
577 ms
ansys.png
577 ms
teh.png
576 ms
2D6EF3_1_0.woff
525 ms
2D6EF3_0_0.woff
525 ms
icomoon.woff
525 ms
2D6EF3_2_0.woff
526 ms
collect
484 ms
ansys_enterprise_with-logo-600x261.jpg
438 ms
start_1-169x169.png
437 ms
collect
52 ms
edr.no accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<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
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
edr.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
edr.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edr.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 Edr.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.
edr.no
Open Graph description is not detected on the main page of Edr. 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: