Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

twincue.com

ゼクシィ縁結び|はじめての婚活を応援する総合婚活サービス

Page Load Speed

7.1 sec in total

First Response

591 ms

Resources Loaded

6.1 sec

Page Rendered

443 ms

About Website

Visit twincue.com now to see the best up-to-date Twincue content and also check out these interesting facts you probably never knew about twincue.com

ゼクシィから生まれた婚活総合サービス「ゼクシィ縁結び」。リクルートが運営する婚活サイト・婚活パーティー・恋活イベント・結婚相談所で、はじめての婚活を応援します。

Visit twincue.com

Key Findings

We analyzed Twincue.com page load time and found that the first response time was 591 ms 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

twincue.com performance score

0

Network Requests Diagram

twincue.com

591 ms

zexy-enmusubi.net

585 ms

zexy-enmusubi.net

921 ms

normalize.css

376 ms

magnific-popup.css

717 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Twincue.com, 68% (72 requests) were made to Zexy-enmusubi.net and 4% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source S.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 334.2 kB (23%)

Content Size

1.4 MB

After Optimization

1.1 MB

In fact, the total size of Twincue.com 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. 30% of websites need less resources to load. Images take 990.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.3 kB

  • Original 28.6 kB
  • After minification 24.0 kB
  • After compression 6.3 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 4.6 kB, which is 16% 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 22.3 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 70.4 kB

  • Original 990.5 kB
  • After minification 920.1 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. Twincue images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 145.0 kB

  • Original 313.2 kB
  • After minification 296.4 kB
  • After compression 168.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 145.0 kB or 46% of the original size.

CSS Optimization

-86%

Potential reduce by 96.5 kB

  • Original 112.8 kB
  • After minification 88.4 kB
  • After compression 16.3 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. Twincue.com needs all CSS files to be minified and compressed as it can save up to 96.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (43%)

Requests Now

96

After Optimization

55

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

SEO Factors

twincue.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twincue.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Twincue.com 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 Twincue. 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: