3.1 sec in total
246 ms
2.5 sec
317 ms
Visit johncarl.net now to see the best up-to-date John Carl content and also check out these interesting facts you probably never knew about johncarl.net
Professional player and instructor of drums in rock, pop, funk, jazz, latin, reggae, fusion, heavy metal and more.
Visit johncarl.netWe analyzed Johncarl.net page load time and found that the first response time was 246 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.
johncarl.net performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value5.1 s
24/100
25%
Value6.6 s
38/100
10%
Value6,630 ms
0/100
30%
Value0.021
100/100
15%
Value12.3 s
15/100
10%
246 ms
361 ms
166 ms
345 ms
269 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 26% of them (21 requests) were addressed to the original Johncarl.net, 45% (37 requests) were made to Fonts.gstatic.com and 23% (19 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Johncarl.net.
Page size can be reduced by 308.4 kB (33%)
926.8 kB
618.4 kB
In fact, the total size of Johncarl.net main page is 926.8 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. Only a small number of websites need less resources to load. Images take 791.8 kB which makes up the majority of the site volume.
Potential reduce by 19.3 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 19.3 kB or 80% of the original size.
Potential reduce by 270.1 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, John Carl needs image optimization as it can save up to 270.1 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 8.2 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 8.2 kB or 14% of the original size.
Potential reduce by 10.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. Johncarl.net needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 21% of the original size.
Number of requests can be reduced by 29 (73%)
40
11
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Carl. 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 from 26 to 1 for CSS and as a result speed up the page load time.
johncarl.net
246 ms
johncarl.net
361 ms
bootstrap.min.css
166 ms
jquery-3.5.1.min.js
345 ms
bootstrap.min.js
269 ms
main.js
239 ms
font-awesome.min.css
269 ms
site.css
286 ms
common.css
287 ms
1.css
317 ms
flag-icon.min.css
417 ms
api.js
37 ms
css
56 ms
css
76 ms
css
69 ms
css
60 ms
css
63 ms
css
67 ms
css
72 ms
css
88 ms
css
89 ms
css
91 ms
css
92 ms
css
97 ms
css
104 ms
css
117 ms
css
120 ms
css
120 ms
css
127 ms
css
127 ms
00810852e1c8c92bb99ba92bb7a1a9a0.jpg
163 ms
8dd7a1fc8933f11af4ebdb4d27c12a77_948x944.png
472 ms
25bac91622e626d1fd3f043f3f592344_240x180.22988505747.png
579 ms
7180467a85b70a02cb40449e3513739c.jpg
236 ms
e349e6d87d163d567676d338bbfa1caa.png
716 ms
4567d7a627a2fdb6357f9b764c542139_349x532.25868725869.png
597 ms
Capture%20it.ttf
1156 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmPuI.ttf
195 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff1GhPuI.ttf
236 ms
pxiEyp8kv8JHgFVrFJA.ttf
193 ms
pxiByp8kv8JHgFVrLGT9V1s.ttf
236 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
236 ms
pxiByp8kv8JHgFVrLFj_V1s.ttf
191 ms
pxiGyp8kv8JHgFVrLPTedw.ttf
306 ms
pxiByp8kv8JHgFVrLEj6V1s.ttf
315 ms
pxiByp8kv8JHgFVrLCz7V1s.ttf
316 ms
pxiByp8kv8JHgFVrLDD4V1s.ttf
309 ms
pxiByp8kv8JHgFVrLBT5V1s.ttf
308 ms
pxiGyp8kv8JHgFVrJJLedw.ttf
316 ms
pxiDyp8kv8JHgFVrJJLmg1hlEA.ttf
310 ms
pxiDyp8kv8JHgFVrJJLm21llEA.ttf
312 ms
pxiDyp8kv8JHgFVrJJLmv1plEA.ttf
312 ms
pxiAyp8kv8JHgFVrJJLmE3tF.ttf
315 ms
pxiDyp8kv8JHgFVrJJLmr19lEA.ttf
317 ms
pxiDyp8kv8JHgFVrJJLmy15lEA.ttf
424 ms
pxiDyp8kv8JHgFVrJJLm111lEA.ttf
427 ms
pxiDyp8kv8JHgFVrJJLm81xlEA.ttf
425 ms
fontawesome-webfont.woff
443 ms
KFOmCnqEu92Fr1Me5Q.ttf
427 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
426 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
428 ms
KFOkCnqEu92Fr1MmgWxP.ttf
429 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
429 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
430 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf
435 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSWaA.ttf
431 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSWaA.ttf
431 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISWaA.ttf
432 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWWaA.ttf
433 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOWaA.ttf
439 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf
439 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOWaA.ttf
438 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOWaA.ttf
438 ms
77b264093e1896cc158b59dfe4f61fde.svg
439 ms
top-ts1427177992.jpg
368 ms
recaptcha__en.js
235 ms
fallback
44 ms
fallback__ltr.css
6 ms
css
32 ms
logo_48.png
3 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
12 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
11 ms
johncarl.net accessibility score
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
Form elements do not have associated labels
Links do not have a discernible name
johncarl.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
johncarl.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Johncarl.net 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 Johncarl.net 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.
johncarl.net
Open Graph data is detected on the main page of John Carl. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: