3.4 sec in total
324 ms
2.5 sec
620 ms
Click here to check amazing WITTE content. Otherwise, check out these important facts you probably never knew about witte.digital
Mit unseren digitalen Lösungen liefern wir Ihnen die Schlüssel zur zukunftsfähigen Mobilität und Logistik.
Visit witte.digitalWe analyzed Witte.digital page load time and found that the first response time was 324 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
witte.digital performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value3.2 s
73/100
25%
Value4.2 s
77/100
10%
Value20 ms
100/100
30%
Value0.417
23/100
15%
Value3.2 s
94/100
10%
324 ms
570 ms
227 ms
338 ms
336 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that all of those requests were addressed to Witte.digital and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Witte.digital.
Page size can be reduced by 71.3 kB (9%)
764.1 kB
692.8 kB
In fact, the total size of Witte.digital main page is 764.1 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. 25% of websites need less resources to load. Images take 682.7 kB which makes up the majority of the site volume.
Potential reduce by 66.0 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 66.0 kB or 81% of the original size.
Potential reduce by 5.3 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. WITTE images are well optimized though.
Number of requests can be reduced by 4 (22%)
18
14
The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WITTE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
witte.digital
324 ms
witte.digital
570 ms
main-0158445559.css
227 ms
styles.css
338 ms
borlabs-cookie_1_de.css
336 ms
language-cookie.js
333 ms
jquery.min.js
448 ms
main-730ec167c6.js
447 ms
borlabs-cookie-prioritize.min.js
340 ms
borlabs-cookie.min.js
337 ms
Logo-63242e5a24.svg
117 ms
Logo_neg-e3648a5964.svg
118 ms
bullets-07c357b4b7.svg
114 ms
hero-start@3x-120x0-c-center.png
222 ms
bg_pattern-604c339689-200x0-c-default.png
115 ms
About-Us_flinkey-200x0-c-center.jpg
1210 ms
NSE_Bild_Header-200x0-c-center.png
335 ms
Digital-Construction-Kit-0x194-c-default.jpg
231 ms
Automotive-DNA-0x194-c-default.jpg
231 ms
Joint-Network-0x194-c-default.jpg
231 ms
EuclidCircularB-Medium-27ece2e51e.woff
408 ms
EuclidCircularB-Regular-0123ead37f.woff
307 ms
EuclidCircularB-Bold-986ed8b4f8.woff
416 ms
witte.digital 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
witte.digital 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
witte.digital 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 Witte.digital 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 Witte.digital 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.
witte.digital
Open Graph data is detected on the main page of WITTE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: