Tools & Wizards About Us
mysupport.dk screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

mysupport.dk

Mysupport har skiftet navn til Diviso - Mysupport.dk

Page Load Speed

4.7 sec in total

First Response

599 ms

Resources Loaded

3.8 sec

Page Rendered

272 ms

mysupport.dk screenshot

About Website

Visit mysupport.dk now to see the best up-to-date Mysupport content for Denmark and also check out these interesting facts you probably never knew about mysupport.dk

1/9-2021 har MySupport skiftet navn til Diviso. Med navneskiftet ønsker Diviso et tydeligere brand med en klar definering af, hvilke opgaver der løses for virksomhedens kunder.

Visit mysupport.dk

Key Findings

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

Performance Metrics

mysupport.dk performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value108.4 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,380 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value71.3 s

0/100

10%

Network Requests Diagram

599 ms

118 ms

gtm.js

73 ms

bootstrap.min.css

142 ms

owl.carousel.css

452 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mysupport.dk, 15% (9 requests) were made to Fonts.gstatic.com and 10% (6 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Diviso.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.2 kB (28%)

Content Size

551.0 kB

After Optimization

394.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mysupport.dk main page is 551.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 381.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 27.6 kB

  • Original 37.4 kB
  • After minification 31.3 kB
  • After compression 9.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 6.1 kB, which is 16% 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 27.6 kB or 74% of the original size.

Image Optimization

-18%

Potential reduce by 18.2 kB

  • Original 98.4 kB
  • After minification 80.2 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. Obviously, Mysupport needs image optimization as it can save up to 18.2 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-28%

Potential reduce by 107.8 kB

  • Original 381.6 kB
  • After minification 370.1 kB
  • After compression 273.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 107.8 kB or 28% of the original size.

CSS Optimization

-8%

Potential reduce by 2.6 kB

  • Original 33.6 kB
  • After minification 33.2 kB
  • After compression 31.0 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. Mysupport.dk has all CSS files already compressed.

Requests Breakdown

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

Requests Now

45

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

599 ms

118 ms

gtm.js

gtm.js

73 ms

bootstrap.min.css

bootstrap.min.css

142 ms

owl.carousel.css

owl.carousel.css

452 ms

667 ms

blueshape.svg

blueshape.svg

612 ms

wave7.svg

wave7.svg

734 ms

playbutton.gif

playbutton.gif

2560 ms

api.js

api.js

55 ms

umbracoforms.js

umbracoforms.js

829 ms

style.css

style.css

726 ms

css2

css2

145 ms

all.min.css

all.min.css

49 ms

920 ms

jquery.validate.min.js

jquery.validate.min.js

63 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

69 ms

2d50d38af9.js

2d50d38af9.js

156 ms

js

js

93 ms

js

js

340 ms

analytics.js

analytics.js

447 ms

destination

destination

415 ms

insight.min.js

insight.min.js

494 ms

dbffdba1-fc51-42f1-94ae-d3e941ea7062.js

dbffdba1-fc51-42f1-94ae-d3e941ea7062.js

498 ms

dreamdata.min.js

dreamdata.min.js

535 ms

fbevents.js

fbevents.js

496 ms

uc.js

uc.js

432 ms

pixel.js

pixel.js

600 ms

api.min.js

api.min.js

480 ms

identify-form.min.js

identify-form.min.js

520 ms

collect

collect

59 ms

collect

collect

225 ms

collect

collect

63 ms

diviso.gif

diviso.gif

1089 ms

mysupport-skifter-navn-til-diviso-low.gif

mysupport-skifter-navn-til-diviso-low.gif

1383 ms

footerwave2.svg

footerwave2.svg

218 ms

logo.png

logo.png

409 ms

insight_tag_errors.gif

insight_tag_errors.gif

238 ms

collect

collect

161 ms

js

js

70 ms

mobile4.png

mobile4.png

348 ms

p

p

193 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff

96 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff

123 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZs.woff

147 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZs.woff

148 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZs.woff

149 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZs.woff

147 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff

149 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZs.woff

128 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZs.woff

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZs.woff

147 ms

ga-audiences

ga-audiences

144 ms

ga-audiences

ga-audiences

93 ms

fa-solid-900.woff

fa-solid-900.woff

18 ms

fa-regular-400.woff

fa-regular-400.woff

38 ms

fa-brands-400.woff

fa-brands-400.woff

44 ms

2d50d38af9.css

2d50d38af9.css

115 ms

font-awesome-css.min.css

font-awesome-css.min.css

13 ms

recaptcha__en.js

recaptcha__en.js

42 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

66 ms

Accessibility Review

mysupport.dk accessibility score

86

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

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

mysupport.dk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

mysupport.dk SEO score

100

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

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mysupport.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mysupport.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

mysupport.dk

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