Tools & Wizards About Us
davidsosnowski.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

davidsosnowski.com

The Music of David Sosnowski

Page Load Speed

3.2 sec in total

First Response

208 ms

Resources Loaded

1.1 sec

Page Rendered

1.8 sec

davidsosnowski.com screenshot

About Website

Click here to check amazing David Sosnowski content. Otherwise, check out these important facts you probably never knew about davidsosnowski.com

The Music of Composer David Sosnowski.

Visit davidsosnowski.com

Key Findings

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

Performance Metrics

davidsosnowski.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

davidsosnowski.com

208 ms

scripts.js

203 ms

i2_styles.css

36 ms

bg_black.jpg

476 ms

player-Realization.htm

463 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that all of those requests were addressed to Davidsosnowski.com and no external sources were called. The less responsive or slowest element that took the longest time to load (476 ms) belongs to the original domain Davidsosnowski.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.2 kB (90%)

Content Size

147.3 kB

After Optimization

15.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Davidsosnowski.com main page is 147.3 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. 20% of websites need less resources to load. HTML takes 140.1 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 129.4 kB

  • Original 140.1 kB
  • After minification 96.8 kB
  • After compression 10.7 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. This page needs HTML code to be minified as it can gain 43.3 kB, which is 31% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 129.4 kB or 92% of the original size.

Image Optimization

-24%

Potential reduce by 1.3 kB

  • Original 5.1 kB
  • After minification 3.9 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. Obviously, David Sosnowski needs image optimization as it can save up to 1.3 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 315 B

  • Original 583 B
  • After minification 493 B
  • After compression 268 B

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 315 B or 54% of the original size.

CSS Optimization

-80%

Potential reduce by 1.2 kB

  • Original 1.5 kB
  • After minification 1.3 kB
  • After compression 311 B

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. Davidsosnowski.com needs all CSS files to be minified and compressed as it can save up to 1.2 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

66

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of David Sosnowski. According to our analytics all requests are already optimized.

Network Requests Diagram

davidsosnowski.com

davidsosnowski.com

208 ms

scripts.js

scripts.js

203 ms

i2_styles.css

i2_styles.css

36 ms

bg_black.jpg

bg_black.jpg

476 ms

player-Realization.htm

player-Realization.htm

463 ms

player-Emergence.htm

player-Emergence.htm

465 ms

player-Discourse.htm

player-Discourse.htm

449 ms

player-event.htm

player-event.htm

451 ms

3c4h.htm

3c4h.htm

444 ms

persistence.htm

persistence.htm

425 ms

player-Lucifer.htm

player-Lucifer.htm

415 ms

player-LuciferDK.htm

player-LuciferDK.htm

411 ms

spheres.htm

spheres.htm

407 ms

spaces.htm

spaces.htm

406 ms

player-revelation.htm

player-revelation.htm

393 ms

player-estuaries.htm

player-estuaries.htm

393 ms

player-devils_sea.htm

player-devils_sea.htm

391 ms

player-3solitudes1.htm

player-3solitudes1.htm

393 ms

player-3solitudes2.htm

player-3solitudes2.htm

393 ms

player-3solitudes3.htm

player-3solitudes3.htm

379 ms

player-epiphany.htm

player-epiphany.htm

377 ms

player-damaged_beauty.htm

player-damaged_beauty.htm

377 ms

player-the_dance.htm

player-the_dance.htm

375 ms

player-Entanglement.htm

player-Entanglement.htm

379 ms

player-Quarks.htm

player-Quarks.htm

374 ms

player-Woman.htm

player-Woman.htm

374 ms

player-Rotations.htm

player-Rotations.htm

341 ms

meditation_1.htm

meditation_1.htm

342 ms

meditation_2.htm

meditation_2.htm

339 ms

player-Sublime_Delta.htm

player-Sublime_Delta.htm

340 ms

player-Kuiper.htm

player-Kuiper.htm

340 ms

player-Ingredients.htm

player-Ingredients.htm

329 ms

player-Woolgathering.htm

player-Woolgathering.htm

328 ms

player-Ruminations.htm

player-Ruminations.htm

326 ms

player-miracle.htm

player-miracle.htm

312 ms

player-Ascension.htm

player-Ascension.htm

273 ms

player-RosaParks.htm

player-RosaParks.htm

235 ms

player-Discomposure.htm

player-Discomposure.htm

223 ms

player-Catherine.htm

player-Catherine.htm

199 ms

player-Weather.htm

player-Weather.htm

74 ms

player-Three_Gaseous_Preludes.htm

player-Three_Gaseous_Preludes.htm

74 ms

player-PS7_ALL_Preview.htm

player-PS7_ALL_Preview.htm

73 ms

player-PS7_1_Preview.htm

player-PS7_1_Preview.htm

73 ms

player-PS7_2_Preview.htm

player-PS7_2_Preview.htm

72 ms

player-PS7_3_Preview.htm

player-PS7_3_Preview.htm

72 ms

player-PS7_4_Preview.htm

player-PS7_4_Preview.htm

71 ms

player-PS7_5_Preview.htm

player-PS7_5_Preview.htm

71 ms

player-South_Mountain.htm

player-South_Mountain.htm

70 ms

player-glance.htm

player-glance.htm

71 ms

player-lightning.htm

player-lightning.htm

70 ms

player-perseids.htm

player-perseids.htm

70 ms

player-first_to_turn.htm

player-first_to_turn.htm

86 ms

player-Something.htm

player-Something.htm

94 ms

player-Prelude_No_5.htm

player-Prelude_No_5.htm

89 ms

player-Prelude_No_5s.htm

player-Prelude_No_5s.htm

93 ms

player-Prelude_No_17.htm

player-Prelude_No_17.htm

93 ms

player-Prelude_No_21.htm

player-Prelude_No_21.htm

92 ms

player-Prelude_No_27.htm

player-Prelude_No_27.htm

114 ms

player-3conversations1.htm

player-3conversations1.htm

107 ms

player-3conversations2.htm

player-3conversations2.htm

108 ms

player-3conversations3.htm

player-3conversations3.htm

108 ms

player-Prelude_No_54.htm

player-Prelude_No_54.htm

107 ms

player-Prelude_for_Four_Hands.htm

player-Prelude_for_Four_Hands.htm

107 ms

1x1_trans.gif

1x1_trans.gif

156 ms

doo-dah.png

doo-dah.png

131 ms

space.gif

space.gif

148 ms

i2_player_off.jpg

i2_player_off.jpg

130 ms

Accessibility Review

davidsosnowski.com accessibility score

64

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

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

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

davidsosnowski.com best practices score

75

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

SEO Factors

davidsosnowski.com SEO score

62

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Davidsosnowski.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 Davidsosnowski.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

davidsosnowski.com

Open Graph description is not detected on the main page of David Sosnowski. 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: