3 sec in total
172 ms
2.7 sec
72 ms
Welcome to breeze-project.com homepage info - get ready to check BREEZE Project best content right away, or after learning these important things about breeze-project.com
Die Unternehmen der BREEZE Group bieten Kunden und Partnern maßgeschneiderte Leistungen in den Bereichen Transport, Logistik und seemäßige Verpackung.
Visit breeze-project.comWe analyzed Breeze-project.com page load time and found that the first response time was 172 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.
breeze-project.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value7.6 s
3/100
25%
Value4.4 s
74/100
10%
Value330 ms
75/100
30%
Value0.001
100/100
15%
Value11.7 s
18/100
10%
172 ms
49 ms
42 ms
37 ms
35 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Breeze-project.com, 23% (18 requests) were made to Static.parastorage.com and 15% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 418.4 kB (10%)
4.1 MB
3.6 MB
In fact, the total size of Breeze-project.com main page is 4.1 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. 55% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 402.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. 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 402.1 kB or 80% of the original size.
Potential reduce by 12.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. BREEZE Project images are well optimized though.
Potential reduce by 3.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 11 (18%)
60
49
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BREEZE Project. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
www.breeze-group.com
172 ms
minified.js
49 ms
focus-within-polyfill.js
42 ms
polyfill.min.js
37 ms
thunderbolt-commons.a79d872a.bundle.min.js
35 ms
main.cd290f82.bundle.min.js
23 ms
main.renderer.1d21f023.bundle.min.js
24 ms
lodash.min.js
25 ms
react.production.min.js
22 ms
react-dom.production.min.js
289 ms
siteTags.bundle.min.js
288 ms
wix-perf-measure.umd.min.js
288 ms
BREEZE%20Logo_negativ.png
455 ms
bundle.min.js
199 ms
4fcc1f_4034e2d266ae4126aaab6f20e8cf2992~mv2.jpg
355 ms
4fcc1f_d51561e9293a44b39522614ea8344d87~mv2.jpg
343 ms
4fcc1f_ec0e0fd569914831ac086803878ea22b~mv2.jpg
393 ms
4fcc1f_2292a21a21584390815e0b76b51d8c82~mv2.jpg
150 ms
4fcc1f_6176ca4399db4f308729c7d04a232cac~mv2.png
303 ms
4fcc1f_d4decfe6e501443e91e98b74e891b4bf~mv2.jpg
361 ms
4fcc1f_09b4110d94e8445b8c5bda6f65fac139~mv2.jpg
543 ms
4fcc1f_49af07e0efdf49ae8731877e89291551~mv2.jpg
545 ms
4fcc1f_fa1c2b9a928c4c67b55acd09589638b4~mv2.jpg
577 ms
4fcc1f_b5debf7393da4a5786017680dc42dcc6~mv2.jpg
576 ms
4fcc1f_0f9d6342c5b14ae99a2f989cb65c5b83~mv2.jpg
691 ms
4fcc1f_82c1a64fc32243d991ed74c7a42f80d2~mv2.jpg
640 ms
4fcc1f_933cc2861d2a4cfab056cc180b3dddd4~mv2.jpg
706 ms
4fcc1f_6d92c3f322b747a095799cef8e5237ab~mv2.jpg
779 ms
4fcc1f_c5891413a3134a4798ed924f7eecf7db~mv2.jpg
843 ms
4fcc1f_1b2f24f578b2483bb664495a690e026d~mv2.jpg
803 ms
4fcc1f_cf2c84862de2420bb7318d6d4a73de77~mv2.jpg
868 ms
4fcc1f_35f9a6911f1b4698b6e17093f682a85d~mv2.jpg
990 ms
4fcc1f_1656f9bc85754518973e189be1c0cd1c~mv2.png
968 ms
4fcc1f_914a33f632dc4b159ebff2736062ced7~mv2.png
784 ms
Icon_standort.png
1036 ms
4fcc1f_07fa899b57274f7e9fdc8242f7ea5e8f~mv2.jpg
1046 ms
4fcc1f_d92c746ef3634223a81832ae715f1cf3~mv2.jpg
1110 ms
4fcc1f_9e08771e44cd42ef91f08cca424dae9e~mv2.jpg
1271 ms
4fcc1f_d35a348d6f784a7f959ca5600dcb81c1~mv2.jpg
1244 ms
4fcc1f_9d91c893f2e24cd1b24a74697d287d10~mv2.jpg
1252 ms
4fcc1f_901469831afc44a39379ad1d8967878a~mv2.jpg
1344 ms
4fcc1f_8427e449b3924958a3bfa6bc7842d1ba~mv2.jpg
1299 ms
4fcc1f_46b707da2b36403d8e25a1507321bd70~mv2.jpg
1502 ms
4fcc1f_fe7ef2886f5a42fb988095b7214c724f~mv2.jpg
1508 ms
4fcc1f_203cc8159f044a43b6870b851df0903b~mv2.jpg
1469 ms
4fcc1f_35da83a16aa049b58d2f0fdc0866a8d5~mv2.jpg
1559 ms
4fcc1f_a9a42d807a254cf6932172411d4e5d3d~mv2.jpg
1563 ms
4fcc1f_03f7469db89e491b9c0e83e232c66e02~mv2.jpg
1547 ms
4fcc1f_43ba68bbc13d4aebbfe795d96b280903~mv2.jpg
1746 ms
FD_Udbezj8EHXbdsqLUplxa1RVmPjeKy21_GQJaLlJI.woff
33 ms
u_mYNr_qYP37m7vgvmIYZxa1RVmPjeKy21_GQJaLlJI.woff
34 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
14 ms
z9rX03Xuz9ZNHTMg1_ghGRa1RVmPjeKy21_GQJaLlJI.woff
112 ms
4udXuXg54JlPEP5iKO5AmRa1RVmPjeKy21_GQJaLlJI.woff
33 ms
4fcc1f_dc078d148a0c4fb8b4780ba3ad8cca95~mv2.jpg
1572 ms
138 ms
135 ms
129 ms
127 ms
123 ms
128 ms
167 ms
164 ms
163 ms
161 ms
157 ms
156 ms
4fcc1f_00d6ae028d9443609e14361db41b4e1a~mv2.jpg
1556 ms
4fcc1f_d2c2946455f94adc9e0d334467751d45~mv2.jpg
1403 ms
4fcc1f_8fea591a8ae84278845038c52ff18967~mv2.jpg
1435 ms
4fcc1f_3b446dc3e8624c55bc6973ae4ceb65d5~mv2.jpg
1221 ms
4fcc1f_00fd3d3ea48948ef8e7f88e6550c6289~mv2.jpg
1475 ms
4fcc1f_93b721ea22fc472cb835b2bdc7ab16ac~mv2.jpg
1549 ms
BREEZE%20Logo_negativ.png
1320 ms
deprecation-en.v5.html
9 ms
bolt-performance
35 ms
deprecation-style.v5.css
11 ms
right-arrow.svg
12 ms
breeze-project.com 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
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
breeze-project.com 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
Page has valid source maps
breeze-project.com SEO score
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 Breeze-project.com 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 Breeze-project.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.
breeze-project.com
Open Graph data is detected on the main page of BREEZE Project. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: