Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

pure-i.net

pure-i.net

Page Load Speed

7.9 sec in total

First Response

1.4 sec

Resources Loaded

6.1 sec

Page Rendered

376 ms

pure-i.net screenshot

About Website

Click here to check amazing Pure I content for Japan. Otherwise, check out these important facts you probably never knew about pure-i.net

出会いならピュアアイ。メアド無しでもご利用可能!理想の恋人探し!

Visit pure-i.net

Key Findings

We analyzed Pure-i.net page load time and found that the first response time was 1.4 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pure-i.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value5,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

pc.pure-i.net

1420 ms

init.css

316 ms

position.js

319 ms

util.js

360 ms

validator.js

704 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pure-i.net, 12% (10 requests) were made to Static.xx.fbcdn.net and 8% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Pc.pure-i.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.7 kB (24%)

Content Size

410.7 kB

After Optimization

313.0 kB

In fact, the total size of Pure-i.net main page is 410.7 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 251.8 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 12.8 kB

  • Original 19.0 kB
  • After minification 17.6 kB
  • After compression 6.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 12.8 kB or 67% of the original size.

Image Optimization

-5%

Potential reduce by 11.5 kB

  • Original 251.8 kB
  • After minification 240.3 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. Pure I images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 32.5 kB

  • Original 90.0 kB
  • After minification 80.9 kB
  • After compression 57.5 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 32.5 kB or 36% of the original size.

CSS Optimization

-82%

Potential reduce by 40.9 kB

  • Original 49.9 kB
  • After minification 39.4 kB
  • After compression 8.9 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. Pure-i.net needs all CSS files to be minified and compressed as it can save up to 40.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (46%)

Requests Now

76

After Optimization

41

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

Accessibility Review

pure-i.net accessibility score

100

Accessibility Issues

Best Practices

pure-i.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

pure-i.net SEO score

92

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

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pure-i.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Pure-i.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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