4.5 sec in total
170 ms
3.8 sec
553 ms
Click here to check amazing Jeremy Siskind content. Otherwise, check out these important facts you probably never knew about jeremysiskind.com
Pianist-composer JEREMY SISKIND is “a genuine visionary” (Indianapolis Star) who “seems to defy all boundaries” (JazzInk) with music “rich in texture and nuance” (Downbeat). A top finisher in several ...
Visit jeremysiskind.comWe analyzed Jeremysiskind.com page load time and found that the first response time was 170 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
jeremysiskind.com performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value23.2 s
0/100
25%
Value20.3 s
0/100
10%
Value6,310 ms
0/100
30%
Value0.338
33/100
15%
Value37.2 s
0/100
10%
170 ms
469 ms
185 ms
198 ms
35 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 33% of them (59 requests) were addressed to the original Jeremysiskind.com, 26% (46 requests) were made to Fonts.gstatic.com and 12% (22 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Jeremysiskind.com.
Page size can be reduced by 729.1 kB (10%)
7.3 MB
6.5 MB
In fact, the total size of Jeremysiskind.com main page is 7.3 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. Only a small number of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.
Potential reduce by 282.5 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 282.5 kB or 85% of the original size.
Potential reduce by 92.6 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. Jeremy Siskind images are well optimized though.
Potential reduce by 320.4 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 320.4 kB or 29% of the original size.
Potential reduce by 33.6 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. Jeremysiskind.com needs all CSS files to be minified and compressed as it can save up to 33.6 kB or 23% of the original size.
Number of requests can be reduced by 108 (89%)
122
14
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jeremy Siskind. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 78 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
jeremysiskind.com
170 ms
jeremysiskind.com
469 ms
mediaelementplayer-legacy.min.css
185 ms
wp-mediaelement.min.css
198 ms
jquery.dataTables.min.css
35 ms
buttons.dataTables.min.css
46 ms
select.dataTables.min.css
60 ms
fixedHeader.dataTables.min.css
49 ms
fixedColumns.dataTables.min.css
53 ms
responsive.dataTables.min.css
51 ms
svgs-attachment.css
202 ms
woocommerce-layout.css
194 ms
woocommerce.css
261 ms
wpmenucart-icons.min.css
194 ms
wpmenucart-main.min.css
267 ms
style.css
319 ms
css
37 ms
testimonial-rotator-style.css
264 ms
font-awesome.min.css
37 ms
name-your-price.min.css
153 ms
style.css
150 ms
jquery.min.js
274 ms
jquery-migrate.min.js
215 ms
gigpress.js
215 ms
jquery.dataTables.min.js
29 ms
dataTables.buttons.min.js
29 ms
buttons.colVis.min.js
29 ms
buttons.print.min.js
29 ms
pdfmake.min.js
53 ms
vfs_fonts.js
72 ms
jszip.min.js
72 ms
buttons.html5.min.js
28 ms
dataTables.select.min.js
44 ms
dataTables.fixedHeader.min.js
47 ms
dataTables.fixedColumns.min.js
45 ms
dataTables.responsive.min.js
49 ms
igsv-datatables.js
216 ms
jsapi
53 ms
igsv-gvizcharts.js
220 ms
jquery.blockUI.min.js
267 ms
add-to-cart.min.js
1978 ms
js.cookie.min.js
1978 ms
woocommerce.min.js
1978 ms
kk-script.js
1979 ms
jquery.cycletwo.js
1979 ms
jquery.cycletwo.addons.js
1978 ms
s-202445.js
37 ms
js
75 ms
gigpress.css
1992 ms
css
30 ms
css
39 ms
wc-blocks.css
1991 ms
style.css
1994 ms
js
127 ms
hooks.min.js
1991 ms
i18n.min.js
1992 ms
main.js
1992 ms
gtm4wp-form-move-tracker.js
1992 ms
gtm4wp-ecommerce-generic.js
1993 ms
gtm4wp-woocommerce.js
1993 ms
idle-timer.min.js
1995 ms
custom.js
1994 ms
mailchimp-woocommerce-public.min.js
1993 ms
e-202445.js
35 ms
scripts.min.js
1998 ms
loader.js
25 ms
smoothscroll.js
1933 ms
jquery.fitvids.js
1923 ms
jquery.mobile.js
1923 ms
easypiechart.js
1922 ms
salvattore.js
1917 ms
sourcebuster.min.js
1855 ms
order-attribution.min.js
1853 ms
common.js
1852 ms
mediaelement-and-player.min.js
1855 ms
mediaelement-migrate.min.js
1852 ms
wp-mediaelement.min.js
1794 ms
jquery.uniform.min.js
1789 ms
custom.js
1789 ms
idle-timer.min.js
1787 ms
loader.js
34 ms
gtm.js
157 ms
Logo-Light.png
794 ms
QqLUDf_vcFA
180 ms
bce9caef-1dda-f923-5b0c-72033d7b330c.jpg
541 ms
5bpVMDw5dK0
381 ms
PSJP2-Cover.jpg
518 ms
IMG_6377-2.heic
973 ms
js-paymentlogos.png
132 ms
premade-image-11.png
131 ms
modules.woff
323 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
323 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
363 ms
S6u9w4BMUTPHh50XSwaPHw.woff
407 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
413 ms
S6uyw4BMUTPHjxAwWA.woff
407 ms
S6uyw4BMUTPHjxAwWw.ttf
413 ms
S6u9w4BMUTPHh7USSwaPHw.woff
413 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
412 ms
S6u8w4BMUTPHh30AUi-s.woff
427 ms
S6u8w4BMUTPHh30AUi-v.ttf
429 ms
KFOkCnqEu92Fr1Mu51xGIzQ.woff
429 ms
KFOkCnqEu92Fr1Mu51xGIzc.ttf
429 ms
KFOjCnqEu92Fr1Mu51S7ACc0CsI.woff
428 ms
KFOjCnqEu92Fr1Mu51S7ACc0CsE.ttf
429 ms
KFOjCnqEu92Fr1Mu51TjASc0CsI.woff
430 ms
KFOjCnqEu92Fr1Mu51TjASc0CsE.ttf
432 ms
KFOiCnqEu92Fr1Mu51QrEz4dKQ.woff
432 ms
KFOiCnqEu92Fr1Mu51QrEz4dKg.ttf
431 ms
KFOjCnqEu92Fr1Mu51TzBic0CsI.woff
431 ms
KFOjCnqEu92Fr1Mu51TzBic0CsE.ttf
430 ms
KFOjCnqEu92Fr1Mu51TLBCc0CsI.woff
448 ms
KFOjCnqEu92Fr1Mu51TLBCc0CsE.ttf
458 ms
KFOmCnqEu92Fr1Mu7GxM.woff
458 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
456 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
458 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
453 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
457 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
460 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
459 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
459 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
458 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
459 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
460 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
461 ms
S6u8w4BMUTPHjxsAUi-s.woff
460 ms
S6u8w4BMUTPHjxsAUi-v.ttf
462 ms
ccc01b768d0d34a9d029d4091.js
453 ms
321 ms
tooltip.css
37 ms
util.css
47 ms
controls.css
47 ms
table.css
48 ms
format.css
46 ms
annotationchart.css
48 ms
jsapi_compiled_default_module.js
272 ms
jsapi_compiled_graphics_module.js
269 ms
jsapi_compiled_ui_module.js
315 ms
jsapi_compiled_corechart_module.js
269 ms
jsapi_compiled_controls_module.js
269 ms
jsapi_compiled_table_module.js
269 ms
jsapi_compiled_annotationchart_module.js
314 ms
jsapi_compiled_annotatedtimeline_module.js
313 ms
jsapi_compiled_gauge_module.js
269 ms
jsapi_compiled_geo_module.js
290 ms
jsapi_compiled_geochart_module.js
312 ms
jsapi_compiled_fw_module.js
312 ms
dygraph-tickers-combined.js
358 ms
jsapi_compiled_timeline_module.js
357 ms
www-player.css
203 ms
www-embed-player.js
202 ms
base.js
202 ms
iframe_api
166 ms
QqLUDf_vcFA
162 ms
5bpVMDw5dK0
172 ms
S6u_w4BMUTPHjxsI9w2_FQfr.woff
143 ms
S6u_w4BMUTPHjxsI9w2_FQfo.ttf
100 ms
88 ms
S6u-w4BMUTPHjxsIPx-mPCQ.woff
58 ms
S6u-w4BMUTPHjxsIPx-mPCc.ttf
58 ms
S6u_w4BMUTPHjxsI5wq_FQfr.woff
57 ms
S6u_w4BMUTPHjxsI5wq_FQfo.ttf
56 ms
S6u_w4BMUTPHjxsI3wi_FQfr.woff
56 ms
www-widgetapi.js
34 ms
S6u_w4BMUTPHjxsI3wi_FQfo.ttf
43 ms
www-player.css
56 ms
www-embed-player.js
74 ms
base.js
98 ms
ad_status.js
157 ms
V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js
79 ms
embed.js
38 ms
id
26 ms
id
45 ms
Create
134 ms
KFOmCnqEu92Fr1Mu4mxM.woff
37 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
38 ms
woocommerce-smallscreen.css
127 ms
jeremysiskind.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.
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.
jeremysiskind.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
Page has valid source maps
jeremysiskind.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jeremysiskind.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 Jeremysiskind.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.
jeremysiskind.com
Open Graph description is not detected on the main page of Jeremy Siskind. 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: