2.1 sec in total
226 ms
1.6 sec
254 ms
Click here to check amazing Elmex content for Germany. Otherwise, check out these important facts you probably never knew about elmex.de
Entdecken Sie unser Sortiment an Zahnpflegeprodukten und finden Sie Informationen zur Mundpflege. Besuchen Sie elmex.de.
Visit elmex.deWe analyzed Elmex.de page load time and found that the first response time was 226 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
elmex.de performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value11.4 s
0/100
25%
Value8.1 s
21/100
10%
Value5,470 ms
0/100
30%
Value0.994
2/100
15%
Value16.4 s
5/100
10%
226 ms
170 ms
229 ms
530 ms
229 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 70% of them (32 requests) were addressed to the original Elmex.de, 11% (5 requests) were made to C.betrad.com and 7% (3 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (530 ms) belongs to the original domain Elmex.de.
Page size can be reduced by 559.3 kB (41%)
1.4 MB
817.9 kB
In fact, the total size of Elmex.de main page is 1.4 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. 35% of websites need less resources to load. Images take 814.8 kB which makes up the majority of the site volume.
Potential reduce by 23.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 6.7 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 23.3 kB or 78% of the original size.
Potential reduce by 144.6 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, Elmex needs image optimization as it can save up to 144.6 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 233.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 233.8 kB or 67% of the original size.
Potential reduce by 157.6 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. Elmex.de needs all CSS files to be minified and compressed as it can save up to 157.6 kB or 85% of the original size.
Number of requests can be reduced by 20 (51%)
39
19
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elmex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
elmex.de
226 ms
www.elmex.de
170 ms
home.cwsp
229 ms
bootstrap.css
530 ms
slick.css
229 ms
slick-theme.css
227 ms
style.css
307 ms
jquery-2.1.4.min.js
392 ms
jquery.isotope.js
311 ms
bootstrap.min.js
379 ms
main.js
237 ms
slick.min.js
388 ms
s_code_remote_h.js
319 ms
s_code_remote_h_post.js
391 ms
s_code_remote_h.js
66 ms
s_code_remote_h_post.js
3 ms
Bootstrap.js
8 ms
headerLogoDesktop.png
90 ms
burger.png
87 ms
topNavArrow.png
83 ms
mobileNavBorder.jpg
85 ms
background.jpg
311 ms
home_logo.png
85 ms
Header_Home%20Page_380x190_elmex%20Kariesschutz%20Prof_Packung.png
323 ms
Homepage_540x250_Elmex%20System%20Packshot.jpg
312 ms
Homepage_540x250_Zahn_Anti%20Karies%20Prof.jpg
409 ms
Homepage_540x250_elmex%20INITIATIVE.jpg
329 ms
Slider%20Image_KinderPack_190x180.png
249 ms
Slider%20Images_190x180_elmex%20Sensitive%20Prof.PNG
334 ms
Slider%20Images_190x180_elmex_Systempackshot_EROSION.png
388 ms
envelope.png
390 ms
arrow_lang.png
406 ms
gaba-gray-logo.png
412 ms
serverComponent.php
18 ms
c9aeeabd-dd65-491d-b4be-3e0db9ae47a0.woff
378 ms
75b36c58-2a02-4057-a537-09af0832ae46.woff
429 ms
h1.js
29 ms
87b9c720423c093e789cbfafb5c04130.js
28 ms
3974.js
100 ms
analytics.js
4 ms
third.js
2 ms
drop_third_party.php
12 ms
3974
18 ms
verify_third_party.php
3 ms
d980aad0-7d56-0132-8394-22000a8b1560.png
112 ms
hover.css
6 ms
elmex.de accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
elmex.de 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
Missing source maps for large first-party JavaScript
elmex.de 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elmex.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Elmex.de 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.
elmex.de
Open Graph description is not detected on the main page of Elmex. 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: