Tools & Wizards About Us
ptr.moe screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ptr.moe

PTR Cloud

Page Load Speed

638 ms in total

First Response

50 ms

Resources Loaded

519 ms

Page Rendered

69 ms

ptr.moe screenshot

About Website

Visit ptr.moe now to see the best up-to-date PTR content and also check out these interesting facts you probably never knew about ptr.moe

Find me!

Visit ptr.moe

Key Findings

We analyzed Ptr.moe page load time and found that the first response time was 50 ms and then it took 588 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

ptr.moe performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.3 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

ptr.moe

50 ms

ptr.moe

88 ms

normalize.css

29 ms

skeleton-dark.css

52 ms

brands.css

38 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 95% of them (20 requests) were addressed to the original Ptr.moe, 5% (1 request) were made to Stats.ptr.moe. The less responsive or slowest element that took the longest time to load (322 ms) relates to the external source Stats.ptr.moe.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.8 kB (16%)

Content Size

29.0 kB

After Optimization

24.2 kB

  • HTML
  • JavaScript

In fact, the total size of Ptr.moe main page is 29.0 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. 15% of websites need less resources to load. Javascripts take 23.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 4.5 kB

  • Original 6.0 kB
  • After minification 4.0 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 33% 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 4.5 kB or 75% of the original size.

JavaScript Optimization

-1%

Potential reduce by 267 B

  • Original 23.0 kB
  • After minification 23.0 kB
  • After compression 22.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.

Requests Breakdown

Number of requests can be reduced by 5 (33%)

Requests Now

15

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ptr.moe

ptr.moe

50 ms

ptr.moe

ptr.moe

88 ms

normalize.css

normalize.css

29 ms

skeleton-dark.css

skeleton-dark.css

52 ms

brands.css

brands.css

38 ms

email-decode.min.js

email-decode.min.js

23 ms

dd168412e25a.js

dd168412e25a.js

322 ms

avatar.webp

avatar.webp

47 ms

gitea.svg

gitea.svg

27 ms

read-cv.svg

read-cv.svg

34 ms

minio-1.svg

minio-1.svg

154 ms

shield-blue.svg

shield-blue.svg

55 ms

immich-logo.svg

immich-logo.svg

60 ms

youtube-music.svg

youtube-music.svg

62 ms

generic-sms.svg

generic-sms.svg

73 ms

stack-overflow.svg

stack-overflow.svg

83 ms

generic-blog.svg

generic-blog.svg

82 ms

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-regular.woff

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-regular.woff

211 ms

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-600.woff

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-600.woff

151 ms

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-700.woff

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-700.woff

260 ms

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-800.woff

open-sans-v34-vietnamese_latin-ext_latin_hebrew_greek-ext_greek_cyrillic-ext_cyrillic-800.woff

187 ms

Accessibility Review

ptr.moe accessibility score

90

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

ptr.moe best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

ptr.moe SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Ptr.moe 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 Ptr.moe 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

ptr.moe

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