Access fencer.wordpress.com. Quirk | It's about Emerson, fencing, painting, writing, absurdities, aikido, politics, spirit, ...

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

fencer.wordpress.com

6 ms

fencer.wordpress.com

20 ms

74 ms

style.css

75 ms

79 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 17% of them (6 requests) were addressed to the original Fencer.wordpress.com, 31% (11 requests) were made to S2.wp.com and 11% (4 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (362 ms) belongs to the original domain Fencer.wordpress.com.

Content Size

652.9 kB

After Optimization

543.9 kB

In fact, the total size of Fencer.wordpress.com main page is 652.9 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. 30% of websites need less resources to load. Images take 376.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 106.8 kB

Original 149.0 kB
After minification 146.7 kB
After compression 42.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 106.8 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

Original 376.0 kB
After minification 374.4 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. Fencer Wordpress images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 304 B

Original 107.0 kB
After minification 107.0 kB
After compression 106.7 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.

CSS Optimization

-1%

Potential reduce by 284 B

Original 20.9 kB
After minification 20.9 kB
After compression 20.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. Fencer.wordpress.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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 the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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 Fencer.wordpress.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 Fencer.wordpress.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 Fencer Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: