Tools & Wizards About Us
megadoor.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

megadoor.com

Megadoor solutions from ASSA ABLOY Entrance Systems

Page Load Speed

915 ms in total

First Response

190 ms

Resources Loaded

668 ms

Page Rendered

57 ms

megadoor.com screenshot

About Website

Welcome to megadoor.com homepage info - get ready to check Megadoor best content right away, or after learning these important things about megadoor.com

Visit megadoor.com

Key Findings

We analyzed Megadoor.com page load time and found that the first response time was 190 ms and then it took 725 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

megadoor.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value2,870 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value20.8 s

2/100

10%

Network Requests Diagram

megadoor.com

190 ms

megadoor-solutions-from-assa-abloy-entrance-systems

189 ms

otSDKStub.js

39 ms

dependencies.lc-68afd0ae080acda4ba7d42f4050b6b0b-lc.min.css

9 ms

global.lc-fb95627d5e6e6f3be0e5f68e12928bd7-lc.min.css

17 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Megadoor.com, 72% (23 requests) were made to Assaabloyentrance.com and 9% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (206 ms) relates to the external source Gw-assets.assaabloy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.8 kB (41%)

Content Size

313.3 kB

After Optimization

185.6 kB

  • HTML
  • JavaScript

In fact, the total size of Megadoor.com main page is 313.3 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. 65% of websites need less resources to load. Javascripts take 272.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 28.5 kB

  • Original 41.3 kB
  • After minification 40.2 kB
  • After compression 12.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. 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 28.5 kB or 69% of the original size.

JavaScript Optimization

-36%

Potential reduce by 99.3 kB

  • Original 272.0 kB
  • After minification 272.0 kB
  • After compression 172.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 99.3 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (92%)

Requests Now

25

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Megadoor. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

megadoor.com

megadoor.com

190 ms

megadoor-solutions-from-assa-abloy-entrance-systems

megadoor-solutions-from-assa-abloy-entrance-systems

189 ms

otSDKStub.js

otSDKStub.js

39 ms

dependencies.lc-68afd0ae080acda4ba7d42f4050b6b0b-lc.min.css

dependencies.lc-68afd0ae080acda4ba7d42f4050b6b0b-lc.min.css

9 ms

global.lc-fb95627d5e6e6f3be0e5f68e12928bd7-lc.min.css

global.lc-fb95627d5e6e6f3be0e5f68e12928bd7-lc.min.css

17 ms

assa-abloy.lc-5907a03f59a8691bca15fe94c8e4e4b0-lc.min.css

assa-abloy.lc-5907a03f59a8691bca15fe94c8e4e4b0-lc.min.css

19 ms

aaes-com.lc-7fe908f67cc09de41c99f5c0adce5b69-lc.min.css

aaes-com.lc-7fe908f67cc09de41c99f5c0adce5b69-lc.min.css

19 ms

environment-display.lc-5ca3c0d194f8d8d04fa324215f49fc86-lc.min.css

environment-display.lc-5ca3c0d194f8d8d04fa324215f49fc86-lc.min.css

22 ms

_a.react.production.min.js

_a.react.production.min.js

24 ms

_b.react-dom.production.min.js

_b.react-dom.production.min.js

19 ms

SmartCropVideoViewer.js

SmartCropVideoViewer.js

56 ms

InteractiveImage.js

InteractiveImage.js

206 ms

gw-group-vendor.lc-98861ee74292a5bad51612ef67058dc4-lc.min.js

gw-group-vendor.lc-98861ee74292a5bad51612ef67058dc4-lc.min.js

97 ms

gw-group-toast.lc-a7530017f0f82a628978fba4472cee84-lc.min.js

gw-group-toast.lc-a7530017f0f82a628978fba4472cee84-lc.min.js

43 ms

clientlibs.lc-08ec84e3a1a8dde34e690c20624fc477-lc.min.css

clientlibs.lc-08ec84e3a1a8dde34e690c20624fc477-lc.min.css

49 ms

gw-group-nav-header.lc-ed22cfa2852ce8b131082d65dd1c2d43-lc.min.js

gw-group-nav-header.lc-ed22cfa2852ce8b131082d65dd1c2d43-lc.min.js

32 ms

gw-group-hero-half-width-image.lc-d29ce674d121c85278fa7a4bdeb14190-lc.min.js

gw-group-hero-half-width-image.lc-d29ce674d121c85278fa7a4bdeb14190-lc.min.js

32 ms

gw-group-text-and-media-two-column-text.lc-21e3141358bcabefc012dd3be0f7d1d7-lc.min.js

gw-group-text-and-media-two-column-text.lc-21e3141358bcabefc012dd3be0f7d1d7-lc.min.js

91 ms

gw-group-cards-grid.lc-6fa10426e56514ea050dc3c0cbab9273-lc.min.js

gw-group-cards-grid.lc-6fa10426e56514ea050dc3c0cbab9273-lc.min.js

39 ms

gw-group-text-and-media-centered.lc-eccfef08dc0319a8ca10fb58bf7421e7-lc.min.js

gw-group-text-and-media-centered.lc-eccfef08dc0319a8ca10fb58bf7421e7-lc.min.js

41 ms

gw-group-form.lc-dc2193a0feed94e8cf5ef1a3dda12f09-lc.min.js

gw-group-form.lc-dc2193a0feed94e8cf5ef1a3dda12f09-lc.min.js

49 ms

gw-group-footer.lc-c1d3e34bd1ae9a2f20af5c03a6f433f8-lc.min.js

gw-group-footer.lc-c1d3e34bd1ae9a2f20af5c03a6f433f8-lc.min.js

71 ms

gtm.js

gtm.js

53 ms

gtm.js

gtm.js

109 ms

76f47613-582f-45a2-8570-be20629c683d.json

76f47613-582f-45a2-8570-be20629c683d.json

31 ms

update.min.js

update.min.js

47 ms

otBannerSdk.js

otBannerSdk.js

21 ms

Roboto-Regular.ttf

Roboto-Regular.ttf

23 ms

Roboto-Medium.ttf

Roboto-Medium.ttf

21 ms

Roboto-Light.ttf

Roboto-Light.ttf

21 ms

Roboto-Thin.ttf

Roboto-Thin.ttf

28 ms

Roboto-Bold.ttf

Roboto-Bold.ttf

20 ms

Accessibility Review

megadoor.com accessibility score

95

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.

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

megadoor.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

megadoor.com SEO score

86

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

Links do not have descriptive text

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

megadoor.com

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