10.6 sec in total
1.8 sec
7.8 sec
1.1 sec
Welcome to beate-leinz.de homepage info - get ready to check Beate LEINZ best content right away, or after learning these important things about beate-leinz.de
Visit beate-leinz.deWe analyzed Beate-leinz.de page load time and found that the first response time was 1.8 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
beate-leinz.de performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value15.4 s
0/100
25%
Value13.6 s
2/100
10%
Value290 ms
79/100
30%
Value0
100/100
15%
Value15.8 s
6/100
10%
1827 ms
651 ms
362 ms
918 ms
347 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Beate-leinz.de, 5% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Leinzeyewear.de.
Page size can be reduced by 6.4 MB (11%)
55.9 MB
49.5 MB
In fact, the total size of Beate-leinz.de main page is 55.9 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. 80% 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. Images take 54.3 MB which makes up the majority of the site volume.
Potential reduce by 132.5 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 132.5 kB or 85% of the original size.
Potential reduce by 5.2 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. Beate LEINZ images are well optimized though.
Potential reduce by 755.3 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 755.3 kB or 70% of the original size.
Potential reduce by 300.2 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. Beate-leinz.de needs all CSS files to be minified and compressed as it can save up to 300.2 kB or 87% of the original size.
Number of requests can be reduced by 14 (19%)
74
60
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Beate LEINZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
leinzeyewear.de
1827 ms
style.min.css
651 ms
style.css
362 ms
frontend.min.css
918 ms
mediaelementplayer-legacy.min.css
347 ms
jquery.min.js
561 ms
jquery-migrate.min.js
339 ms
css2
25 ms
js
56 ms
script.js
464 ms
shared.scripts.min.js
685 ms
frontend.scripts.min.js
354 ms
mediaelement-and-player.min.js
677 ms
mediaelement-migrate.min.js
434 ms
frontend.min.js
563 ms
LEINZ-black.png
134 ms
side-LEINZ_surprise-me.-RD-01_001.png
546 ms
2024.01-Website-1527-x1527-1.surprise-me2.jpg
677 ms
2024.01-Website-1527-x1527-1.surprise-me.jpg
439 ms
2024.01-Website-1527-x1527-1.surprise-me4.jpg
363 ms
2024.01-Website-500-x-700-2.make-me-shine5.jpg
548 ms
2024.01-Website-500-x-700-2.make-me-shine4.jpg
360 ms
2024.01-Website-500-x-700-2.make-me-shine.jpg
475 ms
2024.01-Website-500-x-700-2.make-me-shine3.jpg
476 ms
slider-LEINZ_make-me-shine.SA-03_001-BE-L.png
983 ms
slider-LEINZ_you-are-mine.-BL-03_001.png
930 ms
slider-LEINZ_you-are-mine.-BL-02_001.png
602 ms
2024.01-Website-2000x2829-3.-018-you-are-mine-scaled.jpg
666 ms
2-LEINZ-LZS002GR.protect-me.-Facetune_16-09-2022-15-37-15-5-7.jpg
1192 ms
2-LEINZ-Eyewear-Berlin_Beate_Leinz_Brille_optical-frames_sunglasses_stay-or-go_202101%C2%A9S.Schr%C3%BCnder-5-7-scaled.jpg
1103 ms
2-LEINZ_protect-me.-LZO002-GR.GR-%C2%A9S.Schr%C3%BCnder-5-7-S.jpg
1162 ms
2-LZS001-cr.sa_stay-or-go.-72dpi-1.jpg
790 ms
1-LEINZ_you-and-me.LZS003_rc.sa_%C2%A9S.Schr%C3%BCnder-HR-scaled.jpg
1284 ms
1-LEINZ-LZS003-GN-you-and-me._14-09-2022-22-57-04-2-3-scaled.jpg
1047 ms
1-LEINZ-LZS003-GN-you-and-me._14-09-2022-21-50-57-1-scaled.jpg
1094 ms
LEINZ-Eyewear_you-and-me.-LZS003RD-DSC06472-1_srgb-2-3.jpg
1171 ms
1-LEINZ_Schr%C3%BCnder_-7677-Kayo-Arme-hoch-ret-BL2-2-3.jpg
1593 ms
5-LEINZ-LZX008_BK-LZP008RD-one-life.-DSC06173_final-2-1-scaled.jpg
1218 ms
5-LEINZ-LZX008_BK-LZP008RD-one-life.-DSC06247_final-300-dpi-2-1-scaled.jpg
1271 ms
5-LEINZ-LZX008-BK-one-life.-DSC06221-2-1-scaled.jpg
1286 ms
5-LEINZ-LZX008_BK-one-life.-DSC06201-2-1-scaled.jpg
1302 ms
5-LEINZ-LZP008-RD-one-life.-Clip-DSC06198-X2-1-V2-scaled.jpg
1333 ms
LEINZ-LZX008-BK-one-life.-DSC_5427K-1-scaled.jpg
1383 ms
5-LEINZ-LZP008-BL_GN-one-life.-DSC_5496K-Kopie-scaled.jpg
1398 ms
LEINZ-LZX008-BX-one-life.-DSC_5412K-Kopie-scaled.jpg
1403 ms
2024.01-Website-2560-X1920-5.say-my-name2.jpg
1419 ms
6-LEINZ-LZP011-RD-say-my-name.-DSC_5411K-Kopie-scaled.jpg
1447 ms
6-LEINZ-LZX011-RD-say-my-name.-DSC_5413K-Kopie-scaled.jpg
1495 ms
6-LEINZ-LZP011-GN_GO-say-my-name.-DSC_5512K-Kopie-scaled.jpg
1524 ms
6-LEINZ-LZP011-GN_GO-say-my-name.-DSC-scaled.jpg
1523 ms
6-LEINZ-LZX011-GN-say-my-name.-DSC_5417K-S.jpg
1457 ms
js
132 ms
analytics.js
127 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
232 ms
pxiByp8kv8JHgFVrLFj_V1s.ttf
260 ms
pxiEyp8kv8JHgFVrFJA.ttf
261 ms
pxiByp8kv8JHgFVrLCz7V1s.ttf
288 ms
font.woff
1352 ms
collect
101 ms
6-LEINZ-LZX011-BK-say-my-name.-DSC_5429K-Kopie-scaled.jpg
1249 ms
9-LEINZ-LZP006-CG-go-for-it.-DSC06109-BE-1X1-scaled.jpg
1262 ms
collect
56 ms
9-LEINZ-LZP006-CG-go-for-it.-DSC06104-BE-1X1-scaled.jpg
1207 ms
ga-audiences
35 ms
9-LEINZ-LZP006-CG-go-for-it.-DSC06077-1_srgb-1-1.jpg
1177 ms
9-LEINZ-LZX006-CG-go-for-it.-1-1.jpg
1326 ms
9-LZX006-CG-go-for-it.-3-1-1.jpg
1275 ms
2024.01-Website-1500x1500-go-for-it.jpg
1286 ms
2024.01-Website-1706X2560-your-turn2.jpg
1277 ms
10-LEINZ-LZX005-BK-your-turn.DSC05825_srgb-S.jpg
1099 ms
10-LEINZ-LZS005-SA-your-turn.-16-09-2022-14-20-54-X-scaled.jpg
1087 ms
10-LEINZ-LZS005-SA-your-turn.-16-09-2022-14-19-48-X-scaled.jpg
1091 ms
2024.01-Website-close-your-eyes-3-1.png
1393 ms
7-LEINZ-LZS010-BK-close-your-eyes._DSC06311-scaled.jpg
935 ms
7-LEINZ-LZX010-CG-close-your-eyes._3294-300dpi-S.jpg
885 ms
7-LEINZ-LZS010-BK-close-your-eyes.-XS.jpg
847 ms
7-LEINZ-LZS010-CG-close-your-eyes._16-09-2022-15-17-50-2-3-scaled.jpg
901 ms
LEINZ-x-Guillaume-Larquemain-One-Life-GL-Clip-Web.png
1047 ms
2024.01-Website-1363X1704-GL.jpg
870 ms
2024.01-Website-1363X1704-GL3.jpg
861 ms
2024.01-Website-1363X1704-GL4.jpg
842 ms
2024.01-Website-1363X1704-GL2.jpg
856 ms
Acceptance-Letter-Studio-230712_SS24_Look02_@haydonperrior_BFW-X-scaled.jpg
889 ms
opti2022_hr_1194-scaled.jpg
887 ms
beate-leinz.de accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
beate-leinz.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
beate-leinz.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Beate-leinz.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Beate-leinz.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.
beate-leinz.de
Open Graph description is not detected on the main page of Beate LEINZ. 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: