Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

proactive.dk

Fellowmind | Vi får teknologi til at arbejde for jer

Page Load Speed

2.2 sec in total

First Response

207 ms

Resources Loaded

1.6 sec

Page Rendered

414 ms

proactive.dk screenshot

About Website

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

I Fellowmind skaber vi meningsfulde forbindelser med teknologi, samt omstiller og forbinder virksomheder via teknologi der arbejder for jeres organisation.

Visit proactive.dk

Key Findings

We analyzed Proactive.dk page load time and found that the first response time was 207 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

proactive.dk performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

www.proactive.dk

207 ms

453 ms

fellowmind.css

24 ms

uc.js

22 ms

chunk-vendors.js

63 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Proactive.dk, 87% (34 requests) were made to Fellowmind.com and 3% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (673 ms) relates to the external source Fellowmind.com.

Page Optimization Overview & Recommendations

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

Content Size

3.8 MB

After Optimization

3.7 MB

In fact, the total size of Proactive.dk main page is 3.8 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. 40% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 63.7 kB

  • Original 73.9 kB
  • After minification 53.5 kB
  • After compression 10.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 20.4 kB, which is 28% 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 63.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.5 MB
  • After minification 3.5 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. Proactive images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 29.8 kB

  • Original 193.0 kB
  • After minification 193.0 kB
  • After compression 163.2 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 29.8 kB or 15% of the original size.

CSS Optimization

-32%

Potential reduce by 8.3 kB

  • Original 26.1 kB
  • After minification 26.1 kB
  • After compression 17.8 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. Proactive.dk needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (14%)

Requests Now

37

After Optimization

32

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

Accessibility Review

proactive.dk accessibility score

76

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

High

Links do not have a discernible name

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 IDs are not unique

Best Practices

proactive.dk 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

Page has valid source maps

SEO Factors

proactive.dk SEO score

91

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

    DA

  • Language Claimed

    DA

  • Encoding

    UTF-8

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

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