Tools & Wizards About Us

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pureage.info

纯真年代

Page Load Speed

780 ms in total

First Response

234 ms

Resources Loaded

366 ms

Page Rendered

180 ms

About Website

Visit pureage.info now to see the best up-to-date Pureage content and also check out these interesting facts you probably never knew about pureage.info

纯真年代

Visit pureage.info

Key Findings

We analyzed Pureage.info page load time and found that the first response time was 234 ms and then it took 546 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

pureage.info performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

pureage.info

234 ms

pureage.info

47 ms

jane.min.d8d87b982993a745e5e7b6a6cbf257be8c3e82aab5e485f0908ad7e6c3501ab2.css

14 ms

photoswipe.min.css

17 ms

default-skin.min.css

21 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Pureage.info and no external sources were called. The less responsive or slowest element that took the longest time to load (234 ms) belongs to the original domain Pureage.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.5 kB (66%)

Content Size

167.4 kB

After Optimization

56.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pureage.info main page is 167.4 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. Only 10% of websites need less resources to load. Javascripts take 128.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 19.9 kB

  • Original 24.4 kB
  • After minification 14.1 kB
  • After compression 4.6 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 10.4 kB, which is 42% 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 19.9 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 303 B
  • After minification 303 B

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. Pureage images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 81.0 kB

  • Original 128.6 kB
  • After minification 128.6 kB
  • After compression 47.6 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 81.0 kB or 63% of the original size.

CSS Optimization

-69%

Potential reduce by 9.7 kB

  • Original 14.0 kB
  • After minification 13.4 kB
  • After compression 4.4 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. Pureage.info needs all CSS files to be minified and compressed as it can save up to 9.7 kB or 69% of the original size.

Requests Breakdown

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

Requests Now

8

After Optimization

4

  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

pureage.info accessibility score

94

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.

Best Practices

pureage.info 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

pureage.info 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

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pureage.info can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Pureage.info 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 PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: