3.1 sec in total
288 ms
2.7 sec
165 ms
Visit megacor.at now to see the best up-to-date MEGACOR content and also check out these interesting facts you probably never knew about megacor.at
FASTest® Rapid tests for the detection of antigens and antibodies of bacterial, viral and parasitic pathogens, hormones and inflammation markers as well as MegaFLUO® Immunofluorescence tests and MegaE...
Visit megacor.atWe analyzed Megacor.at page load time and found that the first response time was 288 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
megacor.at performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value6.2 s
11/100
25%
Value6.4 s
40/100
10%
Value90 ms
99/100
30%
Value0.857
4/100
15%
Value6.1 s
64/100
10%
288 ms
200 ms
999 ms
100 ms
199 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that all of those requests were addressed to Megacor.at and no external sources were called. The less responsive or slowest element that took the longest time to load (999 ms) belongs to the original domain Megacor.at.
Page size can be reduced by 132.4 kB (18%)
720.7 kB
588.3 kB
In fact, the total size of Megacor.at main page is 720.7 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. 20% of websites need less resources to load. Images take 603.7 kB which makes up the majority of the site volume.
Potential reduce by 8.1 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 2.3 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 8.1 kB or 78% of the original size.
Potential reduce by 48.4 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. MEGACOR images are well optimized though.
Potential reduce by 59.6 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 59.6 kB or 68% of the original size.
Potential reduce by 16.3 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. Megacor.at needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 83% of the original size.
Number of requests can be reduced by 10 (45%)
22
12
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MEGACOR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
megacor.at
288 ms
www.megacor.at
200 ms
www.megacor.at
999 ms
klaro-dist.css
100 ms
config.js
199 ms
klaro-no-css.js
502 ms
font-awesome.css
298 ms
screen.css
310 ms
slimbox2.css
308 ms
jquery.bxslider.css
307 ms
matchMedia.js
311 ms
jquery-core.js
498 ms
jquery.bxslider.min.js
410 ms
slimbox2.js
410 ms
functions.js
412 ms
flag_germany_75px.png
99 ms
flag_greatbritan_75px.png
102 ms
flag_spain_75px.png
103 ms
megacor_logo.png
99 ms
kind_mitgolden_sonnenblumen_01.jpg
612 ms
junge_katze_couch_01.jpg
617 ms
iso_transparent.png
195 ms
dfa_transparent.png
196 ms
biolago-transparent.png
204 ms
bx_loader.gif
147 ms
megacor.at 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
Links do not have a discernible name
megacor.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
megacor.at 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
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Megacor.at can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Megacor.at 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.
megacor.at
Open Graph description is not detected on the main page of MEGACOR. 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: