2.8 sec in total
50 ms
2.2 sec
535 ms
Visit cobby.io now to see the best up-to-date Cobby content and also check out these interesting facts you probably never knew about cobby.io
Visit cobby.ioWe analyzed Cobby.io page load time and found that the first response time was 50 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 50% of websites can load faster.
cobby.io performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value13.8 s
0/100
25%
Value5.0 s
63/100
10%
Value0 ms
100/100
30%
Value0.005
100/100
15%
Value3.3 s
93/100
10%
50 ms
211 ms
683 ms
14 ms
20 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 75% of them (39 requests) were addressed to the original Cobby.io, 10% (5 requests) were made to Youtube.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (894 ms) belongs to the original domain Cobby.io.
Page size can be reduced by 51.0 kB (6%)
880.0 kB
829.0 kB
In fact, the total size of Cobby.io main page is 880.0 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. 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 436.8 kB which makes up the majority of the site volume.
Potential reduce by 29.2 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 29.2 kB or 78% of the original size.
Potential reduce by 19.0 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. Cobby images are well optimized though.
Potential reduce by 2.7 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.
Potential reduce by 34 B
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. Cobby.io has all CSS files already compressed.
Number of requests can be reduced by 21 (45%)
47
26
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cobby. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
cobby.io
50 ms
cobby.io
211 ms
683 ms
awesomplete.css
14 ms
joomla-alert.min.css
20 ms
template.min.css
20 ms
theme.12.css
49 ms
jquery.min.js
26 ms
jquery-noconflict.min.js
22 ms
awesomplete.min.js
23 ms
core.min.js
29 ms
finder-es5.min.js
213 ms
messages-es5.min.js
222 ms
finder.min.js
37 ms
messages.min.js
37 ms
cookie.min.js
44 ms
uikit.min.js
80 ms
uikit-icons-flow.min.js
79 ms
theme.js
82 ms
gtm.js
114 ms
JBpz1H3TzeQ
155 ms
cobby_logo.svg
22 ms
cobby_logo_weiss.svg
19 ms
zeit2.svg
409 ms
team-manager3.svg
408 ms
steigerung-balken.svg
410 ms
asus_grau-dd74ed7a.png
411 ms
limberry_grau-28839d26.png
411 ms
pickup-moebel_logo-ef0d7b58.png
410 ms
design-bestseller_grau-7ffdf694.png
425 ms
krauterie-logo2-3f67ec67.png
425 ms
tuergriff-shop_grau-9c623ec6.jpeg
425 ms
kniveksperten_grau-237fee4a.png
434 ms
lampen-xxl_grau-df23d4d0.png
570 ms
what_the_cobby_fan_says.svg
571 ms
cobby-preis-aendern2-d6401f9c.jpeg
887 ms
cobby-excel-filter-7b0adc81.jpeg
880 ms
cobby-ampel-469030ce.jpeg
894 ms
cobbyisgreat3.svg
651 ms
footer_shop-systeme2.svg
677 ms
maxcluster_badges_bronzepartner03-7976b1fa.png
687 ms
www-player.css
6 ms
www-embed-player.js
25 ms
base.js
48 ms
ad_status.js
144 ms
XSOeYOgfx9Jh0OnrBRoGZITK3RITQeOfJZOsiQTg9Ss.js
109 ms
embed.js
36 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
38 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
48 ms
id
23 ms
Create
109 ms
GenerateIT
13 ms
cobby.io 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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
cobby.io 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
Browser errors were logged to the console
Page has valid source maps
cobby.io 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cobby.io 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 Cobby.io 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.
cobby.io
Open Graph description is not detected on the main page of Cobby. 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: