7.5 sec in total
1.5 sec
5.9 sec
169 ms
Visit stotzem.com now to see the best up-to-date STOTZEM content and also check out these interesting facts you probably never knew about stotzem.com
In the acoustic guitar world today, Jacques Stotzem is one of the “fingerstyle” guitarists with the most diversified style.
Visit stotzem.comWe analyzed Stotzem.com page load time and found that the first response time was 1.5 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
stotzem.com performance score
1490 ms
138 ms
39 ms
26 ms
27 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 34% of them (30 requests) were addressed to the original Stotzem.com, 24% (21 requests) were made to Encore.scdn.co and 19% (17 requests) were made to Embed-cdn.spotifycdn.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Stotzem.com.
Page size can be reduced by 389.5 kB (29%)
1.4 MB
960.8 kB
In fact, the total size of Stotzem.com main page is 1.4 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. 85% 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. Javascripts take 768.9 kB which makes up the majority of the site volume.
Potential reduce by 43.9 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 43.9 kB or 76% of the original size.
Potential reduce by 5.7 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. STOTZEM images are well optimized though.
Potential reduce by 47.0 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 293.0 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. Stotzem.com needs all CSS files to be minified and compressed as it can save up to 293.0 kB or 64% of the original size.
Number of requests can be reduced by 48 (74%)
65
17
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STOTZEM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
stotzem.com
1490 ms
1708337829-css8b72e7adb02666be3dc156e96477f193615cbef0e4c140fc5ff3a3853def5.css
138 ms
1708337829-cssf7180b40a8d1a4a0706c4e565e6f795a674acb6c9b4605223afcfa751e5c0.css
39 ms
1708337829-css3aa1d88e8da11f94550b4a9fb58e91f2eaf94410ebbfe9589c06ab86e1f8b.css
26 ms
1708337829-css8d852bf1fabd7bab2e46966f36b8ca4c6d4c1f78df07c65cd9870af262249.css
27 ms
1708337829-css31dda86f67bf07dc183a169b26fa5cc53eae6ef82d0636f03e8035a5bf40b.css
24 ms
1708337829-cssc41ac7316c2012612c35e7dbae4783b80f63a4a42ae734d951316fcdb8825.css
32 ms
1708337829-cssef5115b0e9ea87404ea541b096f46f9ccdf62d5ddec1b042d673310a340af.css
36 ms
1708337829-css4d9210cf68184f98db341dbed590f1d3d57a3bfc810147f113f66f59c6d31.css
35 ms
1708337829-css30e962bc66483fe384a6e2f02d756437e8b2b82313c06242ccf5c11555e29.css
34 ms
1708337829-cssd2ed0ecf862462dca5d0f91ca11a1c067eea1c0cec3be637bfd993484621c.css
45 ms
1708337829-csse63637e84c046ab22f62716a036351569bec3b1bb1b81bcc6e030ec1efc47.css
45 ms
1708337829-css7a4233051ddd93ebf8d65f227afd64268a181b1569d149048dd7e5bd6d24d.css
48 ms
1708337829-cssaa1f9604ccb8945ea0950b7c49cb732de7cb17355a57ef946224d6b042525.css
46 ms
jquery.min.js
45 ms
jquery-migrate.min.js
46 ms
gigpress.js
52 ms
cardozafacebook.js
53 ms
1708337829-css2eb52ae604a0a987ddb56fb9e5be84352551b76f62290a2c1ac81fec99c94.css
53 ms
1708337829-css4415ecfc07daf36be89b8f5b4a41acb59d754cef0a7155e28640f0091ab28.css
52 ms
image-cdn.js
54 ms
wp-lightbox-2.min.js
54 ms
wp-slimstat.min.js
79 ms
e-202408.js
32 ms
script_2.1.2.js
55 ms
scripts.js
52 ms
3FkeP4NvDEveDZbEJ9fH6I
540 ms
videoseries
164 ms
VisuelCDStotzemMR.jpg
97 ms
sdk.js
56 ms
BannerSite2024.jpg
60 ms
search.png
26 ms
youtube.png
26 ms
facebook.png
25 ms
instagram.png
28 ms
twitter.png
55 ms
spotify.png
29 ms
sdk.js
37 ms
www-player.css
9 ms
www-embed-player.js
33 ms
base.js
61 ms
ad_status.js
207 ms
jKwdeMg5eTlKLUq1BicdQ3joNHiQFKykZS_8AKWMVTU.js
190 ms
embed.js
55 ms
461cd0504da4fff1.css
81 ms
1f277ca731dbccd5.css
84 ms
be39f1f231deeb23.css
88 ms
polyfills-c67a75d1b6f99dc8.js
100 ms
webpack-86176911189932a2.js
91 ms
framework-9061fa2704610d1a.js
132 ms
main-45d0e026ad3339d5.js
120 ms
_app-97bde41a2afcb6e6.js
169 ms
fec483df-e793d3f4aac0c1fc.js
164 ms
594-284e2b73b8c68654.js
252 ms
396-5ce3af1ccb0ab43d.js
379 ms
745-4ea52882680752d3.js
393 ms
130-d417220083312bc2.js
377 ms
%5Bid%5D-4e8288235fde2652.js
403 ms
_buildManifest.js
402 ms
_ssgManifest.js
417 ms
9PIi6TBTPTBqLK1M3B5YSiyHYMbEqMPaqAIFROrtJLPDOpXi1jhRvR8EyaIet_LqJGgMLxnyXg=s68-c-k-c0x00ffffff-no-rj
248 ms
KFOmCnqEu92Fr1Mu4mxM.woff
91 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
225 ms
id
181 ms
Create
168 ms
CircularSpTitle-Bold-7cd3208b73fd0850bca5d8f7821439cd.woff
432 ms
CircularSpTitle-Black-b063ad0a42cbaf519c7ccba8b3e1caeb.woff
451 ms
CircularSpTitle-Tall-Bold-24c7e518b6e633e498760fab4aa88218.woff
564 ms
CircularSpTitle-Tall-Black-35a438fa59bc07bdf08133e438d72409.woff
466 ms
CircularSp-Arab-Book-15ab1b42ca6ef5894519756031ee3ed5.woff
453 ms
CircularSp-Arab-Bold-f6f9a0b56c26078440d40b145f48ab5a.woff
462 ms
CircularSp-Arab-Black-85253c80e7df46d62c4d5420e1cc5f4c.woff
460 ms
CircularSp-Hebr-Book-d8209975eafc81a9499df8401a339ddd.woff
461 ms
CircularSp-Hebr-Bold-caa03e4cb8690e726ef1625c7d91a7a5.woff
463 ms
CircularSp-Hebr-Black-f52613a9d541248805af1d0bb33102f8.woff
464 ms
CircularSp-Cyrl-Book-6f078f781ee313e298ad8997fd1ffe3d.woff
464 ms
CircularSp-Cyrl-Bold-7e54bccaf45728c472079785d5cd4519.woff
465 ms
CircularSp-Cyrl-Black-b4305d9bf82554f631d2636c3ef90c54.woff
467 ms
CircularSp-Grek-Book-c9de2c0741586c1ab7b6e95541fc7807.woff
467 ms
CircularSp-Grek-Bold-53bb923248ba22cf5554bbe5f434c5c8.woff
467 ms
CircularSp-Grek-Black-49883536c1a3bfc688235ce40572731d.woff
467 ms
CircularSp-Deva-Book-159c0e02bc9dc7dd0830fb569faf1069.woff
479 ms
CircularSp-Deva-Bold-a212adfa8f476d3544664463d5759178.woff
478 ms
CircularSp-Deva-Black-bbe191a7814d06a3eecc724265dae2d0.woff
556 ms
CircularSp-Book-4f217aebee53ffc72f4444f79041ffa5.woff
468 ms
CircularSp-Bold-79ebb2bdea919cebedea4884d08c499e.woff
467 ms
monitoring
509 ms
_error-2d285668fa3a339d.js
135 ms
GenerateIT
25 ms
stotzem.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stotzem.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 Stotzem.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.
stotzem.com
Open Graph description is not detected on the main page of STOTZEM. 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: