Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

oboesolo.com

Official Website of Eugene Izotov, classical oboist | HOME

Page Load Speed

763 ms in total

First Response

110 ms

Resources Loaded

571 ms

Page Rendered

82 ms

oboesolo.com screenshot

About Website

Visit oboesolo.com now to see the best up-to-date Oboesolo content and also check out these interesting facts you probably never knew about oboesolo.com

A brilliant player of dazzling technical ability and musical inventiveness" - San Francisco Chronicle | "There is no finer oboist" - Chicago Tribune | The Official Website of Eugene Izotov, classical ...

Visit oboesolo.com

Key Findings

We analyzed Oboesolo.com page load time and found that the first response time was 110 ms and then it took 653 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

oboesolo.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

www.oboesolo.com

110 ms

originTrials.41d7301a.bundle.min.js

42 ms

minified.js

48 ms

focus-within-polyfill.js

48 ms

polyfill.min.js

47 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Oboesolo.com, 66% (21 requests) were made to Static.parastorage.com and 19% (6 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (249 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.4 kB (45%)

Content Size

579.0 kB

After Optimization

315.6 kB

In fact, the total size of Oboesolo.com main page is 579.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 344.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 260.6 kB

  • Original 344.7 kB
  • After minification 343.1 kB
  • After compression 84.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 260.6 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.6 kB
  • After minification 5.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. Oboesolo images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 228.7 kB
  • After minification 228.7 kB
  • After compression 225.9 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.

Requests Breakdown

Number of requests can be reduced by 11 (65%)

Requests Now

17

After Optimization

6

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oboesolo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

oboesolo.com accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

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

Best Practices

oboesolo.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

oboesolo.com SEO score

100

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

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

Open Graph data is detected on the main page of Oboesolo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: