Report Summary

  • 17

    Performance

    Renders faster than
    36% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 93

    SEO

    Google-friendlier than
    88% of websites

onet.jp

【公式】結婚相談所・婚活するならオーネット O-net

Page Load Speed

13.6 sec in total

First Response

515 ms

Resources Loaded

10.8 sec

Page Rendered

2.3 sec

onet.jp screenshot

About Website

Click here to check amazing O Net content. Otherwise, check out these important facts you probably never knew about onet.jp

結婚相談所なら安心、信頼の「オーネット」。オンライン婚活もお任せください。会員数は業界最大級4.5万人!年間5,180人が成婚。専任アドバイザーと安心の婚活を。最初は無料・結婚チャンステストから。理想の相手を簡単診断。婚活中の会員とのマッチング数、お相手候補のサンプルがもらえます。

Visit onet.jp

Key Findings

We analyzed Onet.jp page load time and found that the first response time was 515 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

onet.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value17,780 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value98.8 s

0/100

10%

Network Requests Diagram

onet.jp

515 ms

onet.rakuten.co.jp

519 ms

common.css

323 ms

frame.css

691 ms

lower.css

346 ms

Our browser made a total of 174 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Onet.jp, 48% (84 requests) were made to Onet.rakuten.co.jp and 7% (13 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Onet.rakuten.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 400.8 kB (28%)

Content Size

1.4 MB

After Optimization

1.0 MB

In fact, the total size of Onet.jp main page is 1.4 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. 65% of websites need less resources to load. Images take 819.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 35.9 kB

  • Original 49.5 kB
  • After minification 46.1 kB
  • After compression 13.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. 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 35.9 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 19.7 kB

  • Original 819.7 kB
  • After minification 800.0 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. O Net images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 287.5 kB

  • Original 473.7 kB
  • After minification 450.5 kB
  • After compression 186.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 287.5 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 57.6 kB

  • Original 69.8 kB
  • After minification 56.1 kB
  • After compression 12.2 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. Onet.jp needs all CSS files to be minified and compressed as it can save up to 57.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 85 (56%)

Requests Now

152

After Optimization

67

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

Accessibility Review

onet.jp accessibility score

85

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

onet.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

onet.jp SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onet.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Onet.jp 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 O Net. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: