6 sec in total
313 ms
4.4 sec
1.2 sec
Visit romeocozma.com now to see the best up-to-date Romeo Cozma content and also check out these interesting facts you probably never knew about romeocozma.com
Romeo Cozma – piano player, composer, conductor, arranger, professor Born on November 13th 1955 in Bucharest,
Visit romeocozma.comWe analyzed Romeocozma.com page load time and found that the first response time was 313 ms and then it took 5.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.
romeocozma.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value27.4 s
0/100
25%
Value17.8 s
0/100
10%
Value8,780 ms
0/100
30%
Value0.008
100/100
15%
Value35.4 s
0/100
10%
313 ms
1340 ms
264 ms
28 ms
521 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 45% of them (45 requests) were addressed to the original Romeocozma.com, 13% (13 requests) were made to Fonts.gstatic.com and 11% (11 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Romeocozma.com.
Page size can be reduced by 957.5 kB (19%)
5.1 MB
4.1 MB
In fact, the total size of Romeocozma.com main page is 5.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. 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. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 71.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 71.2 kB or 79% of the original size.
Potential reduce by 86.2 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. Romeo Cozma images are well optimized though.
Potential reduce by 336.5 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 336.5 kB or 36% of the original size.
Potential reduce by 463.7 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. Romeocozma.com needs all CSS files to be minified and compressed as it can save up to 463.7 kB or 73% of the original size.
Number of requests can be reduced by 48 (61%)
79
31
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Romeo Cozma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
romeocozma.com
313 ms
romeocozma.com
1340 ms
wp-emoji-release.min.js
264 ms
css
28 ms
style.min.css
521 ms
classic-themes.min.css
288 ms
trp-floater-language-switcher.css
222 ms
trp-language-switcher.css
289 ms
style.css
291 ms
bootstrap.min.css
484 ms
template.min.css
706 ms
znb_frontend.css
412 ms
135-layout.css
577 ms
styles.min.css
386 ms
zn_dynamic.css
490 ms
jquery.min.js
620 ms
jquery-migrate.min.js
546 ms
api.js
43 ms
js
63 ms
mediaelementplayer-legacy.min.css
490 ms
wp-mediaelement.min.css
489 ms
plugins.min.js
551 ms
scrollmagic.js
581 ms
znscript.min.js
586 ms
slick.min.js
586 ms
znpb_frontend.bundle.js
697 ms
app.min.js
697 ms
mediaelement-and-player.min.js
901 ms
mediaelement-migrate.min.js
794 ms
wp-mediaelement.min.js
794 ms
recaptcha__ro.js
187 ms
Logo-Romeo-Cozma-230x230_c.jpg
185 ms
download-250x400_c.jpeg
185 ms
New-2-1170x470_c.jpg
186 ms
Romeo-Cozma-1170x470_c.jpg
258 ms
R.-Cozma-2-1170x470_c.jpg
185 ms
272466455_481245803362946_89998280574931437_n-900x500_c.jpg
506 ms
Jazz-Festival-800x1200_c.jpg
965 ms
jAZZ-2-800x1200_c.jpg
1062 ms
Jazz-Festival-500x700_c.jpg
505 ms
272466455_481245803362946_89998280574931437_n.jpg
1290 ms
en_US.png
407 ms
ro_RO.png
504 ms
sdk.js
223 ms
I8xLX7xQOeI
263 ms
videoseries
266 ms
1034 ms
I7GzmrImkuU
267 ms
embed
220 ms
New-Romeo.jpg
1527 ms
FOT_3759-scaled.jpg
1149 ms
analytics.js
243 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
251 ms
kl-social-icons.woff
786 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf
264 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf
297 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf
327 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMB.ttf
326 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf
330 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMB.ttf
330 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMB.ttf
326 ms
glyphicons_halflingsregular.woff
880 ms
sdk.js
115 ms
js
263 ms
www-player.css
14 ms
I8xLX7xQOeI
218 ms
videoseries
668 ms
I7GzmrImkuU
598 ms
anchor
80 ms
mejs-controls.svg
712 ms
196 ms
collect
64 ms
styles__ltr.css
17 ms
recaptcha__ro.js
84 ms
www-player.css
90 ms
www-embed-player.js
109 ms
base.js
137 ms
KkWFeSURekXGycdprVC-UY6ED-ZF5ll2JCMiHhJE2Rk.js
275 ms
webworker.js
359 ms
logo_48.png
350 ms
ad_status.js
401 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
304 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
304 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
304 ms
widget-6-42e06007cafd.js
518 ms
widget-8-3ee99db8f3ae.js
518 ms
widget-9-537c50ebaeb8.js
656 ms
recaptcha__ro.js
223 ms
wAFWjcG1j0S59k6y9gmRkscrkcYt8sjUn-04af-yL2Q.js
138 ms
embed.js
92 ms
id
306 ms
AIf8zZQfOFAOMXVSItIahOdMMeWzGF-uHiqB7-cx6F1A=s68-c-k-c0x00ffffff-no-rj
673 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
193 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
193 ms
print.css
282 ms
Create
409 ms
Create
417 ms
logo-200x120-3190df52.png
128 ms
widget-0-40fa766408e8.js
12 ms
widget-2-00a853ec5bb2.js
11 ms
romeocozma.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
romeocozma.com 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
Page has valid source maps
romeocozma.com 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
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 Romeocozma.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 Romeocozma.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.
romeocozma.com
Open Graph data is detected on the main page of Romeo Cozma. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: