Access pleasekillme.com. Please Kill Me Online - the Uncensored Oral History of Punk

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.148

77/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

pleasekillme.com

67 ms

wp-emoji-release.min.js

19 ms

twentyfourteen.css

20 ms

form_style.css

21 ms

pkm.css

19 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 48% of them (69 requests) were addressed to the original Pleasekillme.com, 15% (21 requests) were made to Pixel.wp.com and 7% (10 requests) were made to Api.pinterest.com. The less responsive or slowest element that took the longest time to load (868 ms) relates to the external source Fonts.gstatic.com.

Content Size

2.6 MB

After Optimization

1.9 MB

In fact, the total size of Pleasekillme.com main page is 2.6 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. 80% 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 105.6 kB

Original 129.1 kB
After minification 125.9 kB
After compression 23.5 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 105.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 13.6 kB

Original 1.5 MB
After minification 1.5 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. Please Kill Me images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 354.1 kB

Original 622.3 kB
After minification 610.4 kB
After compression 268.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 354.1 kB or 57% of the original size.

CSS Optimization

-80%

Potential reduce by 216.5 kB

Original 270.8 kB
After minification 240.8 kB
After compression 54.3 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. Pleasekillme.com needs all CSS files to be minified and compressed as it can save up to 216.5 kB or 80% of the original size.

Requests Now

134

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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.

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

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

pleasekillme.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Please Kill Me Online - the Uncensored Oral History of Punk

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

pleasekillme.com

wp-emoji-release.min.js

twentyfourteen.css

form_style.css

pkm.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

pleasekillme.com

wp-emoji-release.min.js

twentyfourteen.css

form_style.css

pkm.css

settings.css

pac.css

layout.css

woocommerce-layout.css

woocommerce.css

wmlc_client.css

css

genericons.css

style.css

jetpack.css

jquery.js

jquery-migrate.min.js

cntctfrm.js

jquery.themepunch.tools.min.js

jquery.themepunch.revolution.min.js

wmljs.js

jquery.infinitescroll.min.js

adsbygoogle.js

mc-validate.js

add-to-cart.min.js

jquery.blockUI.min.js

woocommerce.min.js

jquery.cookie.min.js

cart-fragments.min.js

masonry.min.js

devicepx-jetpack.js

jquery.masonry.min.js

functions.js

wp-embed.min.js

sharing.js

e-201609.js

style.css

woocommerce-smallscreen.css

analytics.js

pkm_header_2014d.jpg

1364.jpg

29VAUDEVILLE3-articleLarge-1.jpg

Ghost-Child-with-Closed-Eyes.jpg