Tools & Wizards About Us
romeocozma.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

romeocozma.com

Welcome Official Page Romeo Cozma Professor Pianist Composer

Page Load Speed

4.8 sec in total

First Response

304 ms

Resources Loaded

3.7 sec

Page Rendered

803 ms

romeocozma.com screenshot

About Website

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.com

Key Findings

We analyzed Romeocozma.com page load time and found that the first response time was 304 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

romeocozma.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value23.8 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value7,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value32.9 s

0/100

10%

Network Requests Diagram

romeocozma.com

304 ms

romeocozma.com

1361 ms

wp-emoji-release.min.js

278 ms

css

30 ms

style.min.css

492 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 52% of them (45 requests) were addressed to the original Romeocozma.com, 15% (13 requests) were made to Youtube.com and 7% (6 requests) were made to Widget.sndcdn.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Romeocozma.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 977.6 kB (19%)

Content Size

5.1 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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. Only a small number of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 77.3 kB

  • Original 97.3 kB
  • After minification 92.7 kB
  • After compression 20.0 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 77.3 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 88.4 kB

  • Original 3.4 MB
  • After minification 3.3 MB

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.

JavaScript Optimization

-37%

Potential reduce by 348.3 kB

  • Original 953.3 kB
  • After minification 953.1 kB
  • After compression 605.1 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 348.3 kB or 37% of the original size.

CSS Optimization

-75%

Potential reduce by 463.7 kB

  • Original 616.6 kB
  • After minification 608.3 kB
  • After compression 152.9 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 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (63%)

Requests Now

75

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 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 31 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

romeocozma.com

romeocozma.com

304 ms

romeocozma.com

romeocozma.com

1361 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

278 ms

css

css

30 ms

style.min.css

style.min.css

492 ms

classic-themes.min.css

classic-themes.min.css

295 ms

trp-floater-language-switcher.css

trp-floater-language-switcher.css

229 ms

trp-language-switcher.css

trp-language-switcher.css

295 ms

style.css

style.css

305 ms

bootstrap.min.css

bootstrap.min.css

406 ms

template.min.css

template.min.css

712 ms

znb_frontend.css

znb_frontend.css

431 ms

135-layout.css

135-layout.css

589 ms

styles.min.css

styles.min.css

506 ms

zn_dynamic.css

zn_dynamic.css

507 ms

jquery.min.js

jquery.min.js

614 ms

jquery-migrate.min.js

jquery-migrate.min.js

531 ms

api.js

api.js

37 ms

js

js

61 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

506 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

507 ms

plugins.min.js

plugins.min.js

534 ms

scrollmagic.js

scrollmagic.js

587 ms

znscript.min.js

znscript.min.js

811 ms

slick.min.js

slick.min.js

609 ms

znpb_frontend.bundle.js

znpb_frontend.bundle.js

668 ms

app.min.js

app.min.js

669 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

923 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

810 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

810 ms

recaptcha__ro.js

recaptcha__ro.js

189 ms

Logo-Romeo-Cozma-230x230_c.jpg

Logo-Romeo-Cozma-230x230_c.jpg

178 ms

download-250x400_c.jpeg

download-250x400_c.jpeg

178 ms

New-2-1170x470_c.jpg

New-2-1170x470_c.jpg

310 ms

Romeo-Cozma-1170x470_c.jpg

Romeo-Cozma-1170x470_c.jpg

406 ms

R.-Cozma-2-1170x470_c.jpg

R.-Cozma-2-1170x470_c.jpg

289 ms

272466455_481245803362946_89998280574931437_n-900x500_c.jpg

272466455_481245803362946_89998280574931437_n-900x500_c.jpg

290 ms

Jazz-Festival-800x1200_c.jpg

Jazz-Festival-800x1200_c.jpg

581 ms

jAZZ-2-800x1200_c.jpg

jAZZ-2-800x1200_c.jpg

1073 ms

Jazz-Festival-500x700_c.jpg

Jazz-Festival-500x700_c.jpg

405 ms

272466455_481245803362946_89998280574931437_n.jpg

272466455_481245803362946_89998280574931437_n.jpg

1077 ms

en_US.png

en_US.png

405 ms

ro_RO.png

ro_RO.png

581 ms

sdk.js

sdk.js

177 ms

I8xLX7xQOeI

I8xLX7xQOeI

324 ms

videoseries

videoseries

345 ms

387 ms

I7GzmrImkuU

I7GzmrImkuU

345 ms

embed

embed

213 ms

New-Romeo.jpg

New-Romeo.jpg

1108 ms

FOT_3759-scaled.jpg

FOT_3759-scaled.jpg

627 ms

font

font

67 ms

kl-social-icons.woff

kl-social-icons.woff

489 ms

font

font

116 ms

glyphicons_halflingsregular.woff

glyphicons_halflingsregular.woff

511 ms

sdk.js

sdk.js

8 ms

js

js

161 ms

www-player.css

www-player.css

20 ms

www-embed-player.js

www-embed-player.js

19 ms

base.js

base.js

19 ms

I8xLX7xQOeI

I8xLX7xQOeI

215 ms

videoseries

videoseries

218 ms

I7GzmrImkuU

I7GzmrImkuU

213 ms

fallback

fallback

55 ms

mejs-controls.svg

mejs-controls.svg

674 ms

search.js

search.js

22 ms

geometry.js

geometry.js

33 ms

main.js

main.js

38 ms

widget-6-89632d84bf50.js

widget-6-89632d84bf50.js

36 ms

widget-8-60577e767779.js

widget-8-60577e767779.js

37 ms

widget-9-955e62c2a553.js

widget-9-955e62c2a553.js

53 ms

fallback__ltr.css

fallback__ltr.css

6 ms

css

css

119 ms

logo-200x120-3190df52.png

logo-200x120-3190df52.png

17 ms

www-player.css

www-player.css

36 ms

www-embed-player.js

www-embed-player.js

56 ms

base.js

base.js

109 ms

logo_48.png

logo_48.png

33 ms

widget-0-1bf295c4bc65.js

widget-0-1bf295c4bc65.js

282 ms

widget-2-2df17b6ecdf9.js

widget-2-2df17b6ecdf9.js

281 ms

font

font

221 ms

ad_status.js

ad_status.js

425 ms

u3o6s91JBL8hdS-8zlKaE9_QjMMICyQyS6sMo66aQxY.js

u3o6s91JBL8hdS-8zlKaE9_QjMMICyQyS6sMo66aQxY.js

114 ms

embed.js

embed.js

74 ms

print.css

print.css

202 ms

id

id

128 ms

Accessibility Review

romeocozma.com accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

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

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

romeocozma.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

romeocozma.com SEO score

99

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: