Tools & Wizards About Us
eg.dk screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

eg.dk

EG A/S | Markedsledende branchespecifik software i Norden

Page Load Speed

3.1 sec in total

First Response

341 ms

Resources Loaded

2.6 sec

Page Rendered

144 ms

eg.dk screenshot

About Website

Welcome to eg.dk homepage info - get ready to check EG best content for Denmark right away, or after learning these important things about eg.dk

I EG leverer vi fremtidens branchesoftware, der påvirker kunderne og samfundet på en bæredygtig måde - Let's go further!

Visit eg.dk

Key Findings

We analyzed Eg.dk page load time and found that the first response time was 341 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

eg.dk performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

eg.dk

341 ms

eg.dk

486 ms

iframeResizer.min.js

27 ms

screen.css

111 ms

vendor.bundle.js

221 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 89% of them (25 requests) were addressed to the original Eg.dk, 4% (1 request) were made to Cdnjs.cloudflare.com and 4% (1 request) were made to Dl.episerver.net. The less responsive or slowest element that took the longest time to load (840 ms) belongs to the original domain Eg.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 626.4 kB (49%)

Content Size

1.3 MB

After Optimization

655.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eg.dk main page is 1.3 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. 15% of websites need less resources to load. CSS take 643.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 35.7 kB

  • Original 44.5 kB
  • After minification 34.6 kB
  • After compression 8.8 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 9.9 kB, which is 22% 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 35.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 466.1 kB
  • After minification 466.1 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. EG images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 12.3 kB

  • Original 127.6 kB
  • After minification 127.6 kB
  • After compression 115.3 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

-90%

Potential reduce by 578.4 kB

  • Original 643.5 kB
  • After minification 643.2 kB
  • After compression 65.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. Eg.dk needs all CSS files to be minified and compressed as it can save up to 578.4 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (25%)

Requests Now

16

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eg.dk

eg.dk

341 ms

eg.dk

eg.dk

486 ms

iframeResizer.min.js

iframeResizer.min.js

27 ms

screen.css

screen.css

111 ms

vendor.bundle.js

vendor.bundle.js

221 ms

EG.bundle.js

EG.bundle.js

331 ms

find.js

find.js

35 ms

screen.css

screen.css

840 ms

vendor.bundle.js

vendor.bundle.js

446 ms

eg.bundle.js

eg.bundle.js

229 ms

gtm.js

gtm.js

524 ms

eg-logo.svg

eg-logo.svg

110 ms

arrow-right-white.svg

arrow-right-white.svg

107 ms

icon-menu-open-white.svg

icon-menu-open-white.svg

114 ms

icon-search-open-white.svg

icon-search-open-white.svg

215 ms

arrow-btn.svg

arrow-btn.svg

222 ms

eg-kalkia-1000x500.jpg

eg-kalkia-1000x500.jpg

564 ms

eg-sigma-lca-1000x500.jpg

eg-sigma-lca-1000x500.jpg

329 ms

per-aarsleff-1000x500.jpg

per-aarsleff-1000x500.jpg

439 ms

intro-hedensted-kommune.jpg

intro-hedensted-kommune.jpg

633 ms

sprite.symbol.svg

sprite.symbol.svg

426 ms

NeoSansStd-Regular.woff

NeoSansStd-Regular.woff

356 ms

NeoSansStd-Medium.woff

NeoSansStd-Medium.woff

362 ms

NeoSansStd-Bold.woff

NeoSansStd-Bold.woff

453 ms

sprite.symbol.svg

sprite.symbol.svg

116 ms

neosansstd-regular.woff

neosansstd-regular.woff

117 ms

neosansstd-medium.woff

neosansstd-medium.woff

222 ms

neosansstd-bold.woff

neosansstd-bold.woff

214 ms

Accessibility Review

eg.dk accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

eg.dk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eg.dk SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    DA

  • Encoding

    UTF-8

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

eg.dk

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