3.7 sec in total
233 ms
2.8 sec
666 ms
Welcome to tomasz-trzcinski.info homepage info - get ready to check Tomasz Trzcinski best content for Italy right away, or after learning these important things about tomasz-trzcinski.info
Tomasz Trzcinski - Concert Pianist, Composer, Conductor, Arrangeur http://tomasz-trzcinski.info, Piano Explorations: http://pianoexplorations.com, klavierunterricht online
Visit tomasz-trzcinski.infoWe analyzed Tomasz-trzcinski.info page load time and found that the first response time was 233 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
tomasz-trzcinski.info performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value33.1 s
0/100
25%
Value14.4 s
1/100
10%
Value2,310 ms
5/100
30%
Value0.06
98/100
15%
Value26.1 s
0/100
10%
233 ms
542 ms
651 ms
409 ms
495 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 13% of them (20 requests) were addressed to the original Tomasz-trzcinski.info, 11% (18 requests) were made to Cdn-assets.dzcdn.net and 10% (16 requests) were made to Embed-cdn.spotifycdn.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Widget.deezer.com.
Page size can be reduced by 590.3 kB (19%)
3.1 MB
2.5 MB
In fact, the total size of Tomasz-trzcinski.info main page is 3.1 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. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 137.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 137.2 kB or 82% of the original size.
Potential reduce by 45.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. Tomasz Trzcinski images are well optimized though.
Potential reduce by 206.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 206.0 kB or 11% of the original size.
Potential reduce by 201.5 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. Tomasz-trzcinski.info needs all CSS files to be minified and compressed as it can save up to 201.5 kB or 80% of the original size.
Number of requests can be reduced by 99 (70%)
142
43
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomasz Trzcinski. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
tomasz-trzcinski.info
233 ms
tomasz-trzcinski.info
542 ms
muzeum18.jpg
651 ms
menu-2-91.webp
409 ms
menu-2-91.png
495 ms
artist_2504518
129 ms
polska-35.png
406 ms
wielka-brytania-36.png
410 ms
niemcy-35.png
408 ms
tomasz-trzcinski-869-1-658.jpg
642 ms
tomasz-trzcinski-panta-rhei-522.jpeg
642 ms
tomasz-trzcinski-chronos-522.jpeg
734 ms
tomasz-trzcinski-continuum-522.jpeg
689 ms
in.js
16 ms
platform.js
71 ms
adsbygoogle.js
191 ms
video-1556.png
711 ms
like.php
261 ms
widgets.js
37 ms
37i9dQZF1DZ06evO47q2Ny
533 ms
141651321
815 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
57 ms
subscribe_embed
187 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
39 ms
html_widget_53-datauri.css
158 ms
html_widget_53.js
158 ms
settings
244 ms
postmessageRelay
169 ms
Codystar-Regular.woff
511 ms
Lato-Regular.woff
600 ms
Lustria-Regular.woff
595 ms
AllertaStencil-Regular.woff
626 ms
JosefinSans-SemiBold.woff
705 ms
show_ads_impl.js
258 ms
www-subscribe-embed_split_v0.css
9 ms
www-subscribe-embed_v0.js
28 ms
1
77 ms
subscribe_button_branded_lozenge.png
18 ms
loading_indicator.gif
21 ms
1x1_pixel.png
20 ms
facebook_share.png
21 ms
embed_share.png
21 ms
email_share.png
21 ms
reverbnationlogo.png
22 ms
cb=gapi.loaded_0
9 ms
5_XuFSvudYy.js
57 ms
FEppCFCt76d.png
64 ms
3192416480-postmessagerelay.js
50 ms
rpc:shindig_random.js
32 ms
error-page.167c5854.css
37 ms
optimize.js
61 ms
gtm.ea4c34bc.js
53 ms
retargeting-pixels.5ab9cdc0.js
61 ms
error-page-logo.24aca703.svg
84 ms
bounce
14 ms
cb=gapi.loaded_2
16 ms
bounce
45 ms
cb=gapi.loaded_0
21 ms
border_3.gif
16 ms
subscribe_embed
63 ms
spacer.gif
24 ms
bubbleSprite_3.png
25 ms
bubbleDropR_3.png
24 ms
bubbleDropB_3.png
27 ms
5_XuFSvudYy.js
27 ms
button.856debeac157d9669cf51e73a08fbc93.js
19 ms
www-subscribe-embed-card_v0.css
3 ms
www-subscribe-embed-card_v0.js
4 ms
embeds
38 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.pl.html
24 ms
zrt_lookup.html
40 ms
ads
387 ms
ads
430 ms
fd67e1fb69fabcc3.css
40 ms
c5abdefd4f05694f.css
72 ms
45ac58c8f877602b.css
73 ms
polyfills-78c92fac7aa8fdd8.js
80 ms
webpack-d5e915a063b63068.js
95 ms
framework-1c912989c69ab413.js
99 ms
main-4ab1044a8a334553.js
97 ms
_app-2c232d8d36f1b22d.js
105 ms
fec483df-893841093599befa.js
97 ms
370d8c6a-ba7b9fa33b972102.js
95 ms
2049-f4817b444e193068.js
103 ms
194-d2f4368186f3823d.js
97 ms
3666-5f9cd5919503457a.js
104 ms
%5Bid%5D-f852a6d5e0c3e2c5.js
118 ms
_buildManifest.js
118 ms
_ssgManifest.js
118 ms
light_share_close.png
11 ms
like.php
225 ms
plusone.js
9 ms
ga.js
56 ms
controller_background.png
5 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
19 ms
cb=gapi.loaded_0
19 ms
cb=gapi.loaded_1
15 ms
fastbutton
39 ms
settings
33 ms
postmessageRelay
58 ms
__utm.gif
27 ms
__utm.gif
28 ms
inter.css
43 ms
deezer-product.css
42 ms
c57b5bdef12017a6.css
42 ms
polyfills-78c92fac7aa8fdd8.js
538 ms
webpack-4d50e23a049cfe20.js
43 ms
framework-e51163eae4b843dc.js
48 ms
main-537daf4c47c6d130.js
48 ms
_app-60a14b76c078232e.js
52 ms
8864-2bb0e8ad84331f78.js
50 ms
9655-819fa905da276f6b.js
53 ms
7797-b15fcd116c7dffea.js
52 ms
%5B...slug%5D-dcd232fba5132d01.js
313 ms
_buildManifest.js
53 ms
_ssgManifest.js
53 ms
RhLV4
1025 ms
embeds
49 ms
site.75180e.css
168 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.en.html
24 ms
developers.google.com
944 ms
reactive_library.js
159 ms
ca-pub-5910821563230283
93 ms
5_XuFSvudYy.js
8 ms
__utm.gif
5 ms
inter-regular.2ac284d7ba9dd63e691ea7afc14d163891a6a9bb.woff
13 ms
inter-semibold.12858343548d78b46410bee99a30aed4ba830817.woff
14 ms
inter-bold.8fbb01ba66d2a2ed461d4459f73236231bd5188f.woff
13 ms
inter-black.50170d884099471742152d0191b49a9a80873200.woff
13 ms
Muli-Regular.woff
284 ms
ads
247 ms
ads
384 ms
gen_204
59 ms
pixel
217 ms
9831594704369569470
48 ms
abg_lite.js
36 ms
omrhp.js
36 ms
Q12zgMmT.js
45 ms
window_focus.js
50 ms
qs_click_protection.js
53 ms
ufs_web_display.js
38 ms
fullscreen_api_adapter.js
173 ms
interstitial_ad_frame.js
177 ms
pixel
205 ms
B31965939.393355372;dc_trk_aid=585290422;dc_trk_cid=214873221;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr=;gdpr_consent=;ltd=;tpsrc=cis;dc_tdv=1
198 ms
icon.png
27 ms
1237811204532316447
28 ms
gen_204
199 ms
62bHydCX.html
158 ms
activeview
68 ms
pixel
54 ms
pixel
55 ms
XCSEbScD2TvrcCbmOAwzw3FcKGiduMdvSHMNJDgnGcc.js
9 ms
rum
97 ms
pixel
94 ms
setuid
94 ms
__utm.gif
26 ms
pixel
32 ms
rum
24 ms
tomasz-trzcinski.info accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
tomasz-trzcinski.info best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
tomasz-trzcinski.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomasz-trzcinski.info can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Tomasz-trzcinski.info 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.
tomasz-trzcinski.info
Open Graph data is detected on the main page of Tomasz Trzcinski. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: