4.7 sec in total
339 ms
3.9 sec
408 ms
Click here to check amazing Brillebitte content. Otherwise, check out these important facts you probably never knew about brillebitte.de
Visit brillebitte.deWe analyzed Brillebitte.de page load time and found that the first response time was 339 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
brillebitte.de performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value14.0 s
0/100
25%
Value13.0 s
2/100
10%
Value2,080 ms
7/100
30%
Value1.888
0/100
15%
Value14.5 s
9/100
10%
339 ms
1168 ms
26 ms
38 ms
229 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 94% of them (96 requests) were addressed to the original Brillebitte.de, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Brillebitte.de.
Page size can be reduced by 1.0 MB (62%)
1.7 MB
642.5 kB
In fact, the total size of Brillebitte.de main page is 1.7 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. 60% of websites need less resources to load. Javascripts take 900.2 kB which makes up the majority of the site volume.
Potential reduce by 52.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 13.6 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 52.1 kB or 86% of the original size.
Potential reduce by 46.7 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, Brillebitte needs image optimization as it can save up to 46.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 685.0 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 685.0 kB or 76% of the original size.
Potential reduce by 263.8 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. Brillebitte.de needs all CSS files to be minified and compressed as it can save up to 263.8 kB or 85% of the original size.
Number of requests can be reduced by 38 (39%)
97
59
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brillebitte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
brillebitte.de
339 ms
www.brillebitte.de
1168 ms
css
26 ms
css
38 ms
jquery-1.7.min.js
229 ms
superfish.js
219 ms
jquery.easing.1.3.js
220 ms
jquery.mobile.customized.min.js
222 ms
scripts.js
223 ms
jquery.jcarousel.min.js
226 ms
font-awesome.css
327 ms
extra_style.css
330 ms
grid_1170.css
330 ms
styles.css
443 ms
responsive.css
332 ms
superfish.css
333 ms
camera.css
429 ms
widgets.css
431 ms
jquery-ui.css
431 ms
cloud-zoom.css
440 ms
trustedrating.css
455 ms
catalogsale.css
535 ms
prototype.js
652 ms
ccard.js
539 ms
validation.js
550 ms
builder.js
548 ms
effects.js
552 ms
dragdrop.js
643 ms
controls.js
646 ms
slider.js
674 ms
js.js
675 ms
form.js
676 ms
translate.js
749 ms
cookies.js
753 ms
jquery-ui-1.10.2.custom.min.js
877 ms
cloud-zoom.1.0.2.min.js
767 ms
bootstrap.js
770 ms
jquery.equalizer.min.js
772 ms
carousel.js
855 ms
camera.js
862 ms
body-bg.gif
127 ms
ga.js
125 ms
logo.png
179 ms
rxxXUYj4oZ6Q5oDJFtEd6hsxEYwM7FgeyaSgU71cLG0.woff
105 ms
fontawesome-webfont.woff
217 ms
nav-container.gif
176 ms
marker-8.gif
175 ms
fotolia_80378274.jpg
176 ms
damenbrillen.jpg
200 ms
herrenbrillen.jpg
211 ms
sonnenbrillen.jpg
224 ms
banners-5.jpg
225 ms
photo002_6.jpg
225 ms
photo002_5_1.jpg
310 ms
photo002_4_1.jpg
319 ms
photo002_4_6.jpg
321 ms
photo002_4_7.jpg
322 ms
photo002_4_8.jpg
327 ms
photo002_4_9.jpg
333 ms
photo002_4_11.jpg
418 ms
photo002_4_12.jpg
427 ms
andy_wolf.png
428 ms
bering.png
431 ms
calypso.png
434 ms
casio.png
442 ms
coeur_de_lion.png
527 ms
diesel.png
558 ms
dolce_gabbana.png
533 ms
dugena.png
562 ms
emporio_armani.png
580 ms
engelsrufer.png
552 ms
etnia.png
637 ms
festina.png
642 ms
flair.png
664 ms
fossil.png
666 ms
freudenhaus.png
668 ms
goerge_gina_lucy.png
688 ms
ice.png
747 ms
tilmJBBU81h1G7ZsdY3Hmw.woff
73 ms
jette.png
655 ms
__utm.gif
30 ms
lapponia_jewelry.png
612 ms
leonardo.png
609 ms
lindberg.png
612 ms
maui_jim.png
631 ms
mykita.png
669 ms
nike.png
656 ms
pepe_jeans.png
669 ms
ray-ban.png
671 ms
rodenstock.png
667 ms
schmuck_werk.png
677 ms
swarovski.png
663 ms
theo.png
656 ms
thomas_sabo.png
677 ms
ti_sento.png
677 ms
tom_ford.png
676 ms
xen.png
692 ms
toogle-button.png
660 ms
camera-loader.gif
656 ms
slide1.jpg
676 ms
slide2.jpg
222 ms
print.css
113 ms
brillebitte.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
brillebitte.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
brillebitte.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brillebitte.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Brillebitte.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.
brillebitte.de
Open Graph description is not detected on the main page of Brillebitte. 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: