Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 95

    SEO

    Google-friendlier than
    91% of websites

contrariwise.org

Contrariwise: Literary Tattoos • The original literary tattoo blog! Over 600 tattoos from books, poetry, music, and other sources.

Page Load Speed

2.8 sec in total

First Response

74 ms

Resources Loaded

1.2 sec

Page Rendered

1.6 sec

contrariwise.org screenshot

About Website

Click here to check amazing Contrariwise content for United States. Otherwise, check out these important facts you probably never knew about contrariwise.org

Contrariwise: Literary Tattoos is a blog about tattoos based on books, poems, lyrics, quotes, and other sources.

Visit contrariwise.org

Key Findings

We analyzed Contrariwise.org page load time and found that the first response time was 74 ms and then it took 2.8 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

contrariwise.org performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value410 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

contrariwise.org

74 ms

www.contrariwise.org

113 ms

jU9BDsIwDPvQSuDEc1DVhimjbaIm07TfE2BCQ3DgZsdO7BxhxIZKCmprweEEiZvFZOHKvYYzUEtlzqiQdPPosHDP0tEHi4S3YVKomCliwYrNPoiUuGI_VGp_Lru2595LqUrBoJwolkBec9fJ9QlNYrpB5Tx7SVgoj2gKxhKE1b6dF09_vt9f137Cnf-RtuE7.css

7 ms

jY1tCoAgEEQvpG0dyXSR1fUjV5FuX0G_Ixh4DLxhZmmuNhSBWTVly8OhQLhzDGznCzV_aTqRb6bjkiirDQL2amyEVNzgW-_E6LQ3zM_ko6kVPGYUEmDanxuJVDVTjnIB.js

54 ms

adsbygoogle.js

15 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 28% of them (25 requests) were addressed to the original Contrariwise.org, 17% (15 requests) were made to Pixel.wp.com and 8% (7 requests) were made to Api.pinterest.com. The less responsive or slowest element that took the longest time to load (545 ms) relates to the external source Graph.facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.3 kB (10%)

Content Size

1.5 MB

After Optimization

1.4 MB

In fact, the total size of Contrariwise.org main page is 1.5 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. 75% 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.2 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 66.2 kB

  • Original 83.0 kB
  • After minification 83.0 kB
  • After compression 16.8 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 66.2 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.2 MB
  • After minification 1.2 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. Contrariwise images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 80.1 kB

  • Original 207.4 kB
  • After minification 202.3 kB
  • After compression 127.2 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 80.1 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (50%)

Requests Now

80

After Optimization

40

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

Accessibility Review

contrariwise.org accessibility score

90

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Best Practices

contrariwise.org best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

contrariwise.org SEO score

95

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Contrariwise.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Contrariwise.org 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 Contrariwise. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: