7.6 sec in total
391 ms
5.1 sec
2.1 sec
Visit comma.com now to see the best up-to-date Comma content and also check out these interesting facts you probably never knew about comma.com
99% der Aufgaben lösen wir mit Code, Analytics & mit Ihrem Team, 1% mit PowerPoint – in Co-Creation mit Ihren Mitarbeiter:innen & ganz pragmatisch.
Visit comma.comWe analyzed Comma.com page load time and found that the first response time was 391 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
comma.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value12.3 s
0/100
25%
Value14.7 s
1/100
10%
Value16,680 ms
0/100
30%
Value0
100/100
15%
Value27.2 s
0/100
10%
391 ms
460 ms
665 ms
350 ms
343 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Comma.com, 92% (58 requests) were made to Comma-soft.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Comma-soft.com.
Page size can be reduced by 238.1 kB (15%)
1.6 MB
1.4 MB
In fact, the total size of Comma.com main page is 1.6 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. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 145.8 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 145.8 kB or 90% of the original size.
Potential reduce by 92.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. Comma images are well optimized though.
Potential reduce by 51 B
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 9 (17%)
53
44
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Comma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
comma.com
391 ms
comma.com
460 ms
comma-soft.com
665 ms
autoptimize_43cd8d92b083f6965f11459d0c24e8a4.css
350 ms
autoptimize_single_2293ceca1e724d9c7ac34471f409ff20.css
343 ms
jquery.min.js
468 ms
autoptimize_single_d1b35351a032caef021101f4aba5d070.js
736 ms
borlabs-cookie-prioritize.min.js
336 ms
api.js
42 ms
regenerator-runtime.min.js
346 ms
wp-polyfill.min.js
348 ms
autoptimize_single_6a0e8318d42803736d2fafcc12238026.js
348 ms
jquery-migrate.min.js
349 ms
borlabs-cookie.min.js
349 ms
logo-46bc2ab6ce.svg
162 ms
logo-46bc2ab6ce.svg
182 ms
logo-white-dc4078d1cb.svg
183 ms
iStock-1270949626-1-870x580-c-default.jpg
1158 ms
03_ViKo_FF_8548_web-1-870x580-c-default.jpg
1124 ms
iStock-903141924-870x580-c-default.jpg
1124 ms
allianz-120x0-c-default.png
870 ms
arag-120x0-c-default.png
872 ms
audi-120x0-c-default.png
869 ms
axa-120x0-c-default.png
1151 ms
bitmark-120x0-c-default.png
1155 ms
boehringer-ingelheim-120x0-c-default.png
1154 ms
cosmos-direct-120x0-c-default.png
1167 ms
daimler-120x0-c-default.png
1167 ms
debeka-120x0-c-default.png
1169 ms
devk-120x0-c-default.png
1168 ms
dhl-120x0-c-default.png
1169 ms
dihk-120x0-c-default.png
1170 ms
dlr-120x0-c-default.png
1214 ms
ergo-120x0-c-default.png
1221 ms
fresenius-netcare-120x0-c-default.png
1214 ms
gkv-120x0-c-default.png
1215 ms
gothaer-120x0-c-default.png
1221 ms
huk-coburg-120x0-c-default.png
1225 ms
kfw-120x0-c-default.png
1240 ms
kostal-120x0-c-default.png
1241 ms
kvwl-120x0-c-default.png
1243 ms
otto-fuchs-120x0-c-default.png
1242 ms
phoenix-contact-120x0-c-default.png
1243 ms
porsche-120x0-c-default.png
1332 ms
postbank-120x0-c-default.png
1340 ms
rwe-120x0-c-default.png
1344 ms
sms-group-120x0-c-default.png
1345 ms
telekom-120x0-c-default.png
1347 ms
tuev-rheinland-120x0-c-default.png
1316 ms
Segma-Regular-60e55e2287.woff
1268 ms
Segma-Medium-84e9c06d3e.woff
1360 ms
Segma-Semibold-8d00b54907.woff
1543 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
4 ms
IvarDisplay-Medium-ed5c6b22e4.woff
1357 ms
recaptcha__en.js
684 ms
silkamono-regular-webfont.woff
687 ms
silkamono-medium-webfont.woff
673 ms
thyssen-krupp-120x0-c-default.png
852 ms
viega-120x0-c-default.png
604 ms
villeroy-boch-120x0-c-default.png
578 ms
iStock-939501750-800x0-c-default.jpg
717 ms
villa_hammerschmidt_petersberger_gespraeche-800x0-c-default.png
1065 ms
02_Arena_FF_8043x_web-1-800x0-c-default.jpg
715 ms
comma.com 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
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
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.
comma.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
comma.com 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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Comma.com 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 Comma.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.
comma.com
Open Graph data is detected on the main page of Comma. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: