Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

usagi.pl

Default page

Page Load Speed

2.7 sec in total

First Response

504 ms

Resources Loaded

1.9 sec

Page Rendered

244 ms

usagi.pl screenshot

About Website

Visit usagi.pl now to see the best up-to-date Usagi content and also check out these interesting facts you probably never knew about usagi.pl

Default page

Visit usagi.pl

Key Findings

We analyzed Usagi.pl page load time and found that the first response time was 504 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

usagi.pl performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

usagi.pl

504 ms

base.css

121 ms

skeleton.css

333 ms

prettyPhoto.css

335 ms

jquery.js

470 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 93% of them (26 requests) were addressed to the original Usagi.pl, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (921 ms) belongs to the original domain Usagi.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.2 kB (14%)

Content Size

1.1 MB

After Optimization

987.3 kB

In fact, the total size of Usagi.pl main page is 1.1 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. 35% of websites need less resources to load. Images take 961.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 13.6 kB

  • Original 17.0 kB
  • After minification 14.8 kB
  • After compression 3.4 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 2.2 kB, which is 13% 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 13.6 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 31.7 kB

  • Original 961.5 kB
  • After minification 929.8 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. Usagi images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 80.1 kB

  • Original 129.3 kB
  • After minification 123.6 kB
  • After compression 49.3 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 62% of the original size.

CSS Optimization

-87%

Potential reduce by 31.8 kB

  • Original 36.7 kB
  • After minification 28.5 kB
  • After compression 4.8 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. Usagi.pl needs all CSS files to be minified and compressed as it can save up to 31.8 kB or 87% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

27

After Optimization

27

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

Accessibility Review

usagi.pl accessibility score

79

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Best Practices

usagi.pl best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

usagi.pl 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 Usagi.pl 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 Usagi.pl 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 description is not detected on the main page of Usagi. 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: