Tools & Wizards About Us
twincue.com screenshot

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

twincue.com screenshot

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

  • HTML
  • Images
  • JavaScript
  • CSS

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

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

twincue.com

twincue.com

591 ms

zexy-enmusubi.net

zexy-enmusubi.net

585 ms

zexy-enmusubi.net

zexy-enmusubi.net

921 ms

normalize.css

normalize.css

376 ms

magnific-popup.css

magnific-popup.css

717 ms

common.css

common.css

1184 ms

index.css

index.css

512 ms

jquery.js

jquery.js

1198 ms

person.js

person.js

517 ms

overlay.css

overlay.css

544 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

681 ms

lp_main.js

lp_main.js

689 ms

rm.js

rm.js

46 ms

jquery.min.js

jquery.min.js

29 ms

jquery.easing.min.js

jquery.easing.min.js

509 ms

jquery.scrollFade.js

jquery.scrollFade.js

646 ms

jquery.bgswitcher.js

jquery.bgswitcher.js

827 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

678 ms

jquery.cookie.js

jquery.cookie.js

680 ms

common.js

common.js

815 ms

s_code.js

s_code.js

1087 ms

code_to_paste.js

code_to_paste.js

847 ms

fbds.js

fbds.js

158 ms

ep.js

ep.js

79 ms

fbevents.js

fbevents.js

158 ms

arw_pink_menu_pc.png

arw_pink_menu_pc.png

181 ms

logo_01.png

logo_01.png

182 ms

logo_02.png

logo_02.png

186 ms

ico_gnav_01_pc.png

ico_gnav_01_pc.png

184 ms

ico_gnav_02_pc.png

ico_gnav_02_pc.png

184 ms

ico_gnav_03_pc.png

ico_gnav_03_pc.png

186 ms

ico_gnav_04_pc.png

ico_gnav_04_pc.png

344 ms

ico_gnav_05_pc_hover.png

ico_gnav_05_pc_hover.png

345 ms

ico_gnav_05_pc.png

ico_gnav_05_pc.png

342 ms

top_image_p1.png

top_image_p1.png

510 ms

top_image_p2.png

top_image_p2.png

347 ms

top_image_p3.png

top_image_p3.png

516 ms

top_image_p4.png

top_image_p4.png

680 ms

top_image_p5.png

top_image_p5.png

681 ms

arw_pink_movie.png

arw_pink_movie.png

511 ms

bird.png

bird.png

517 ms

txt_about.png

txt_about.png

681 ms

img_about01.png

img_about01.png

683 ms

arw_gray_pc.png

arw_gray_pc.png

688 ms

img_about02.png

img_about02.png

692 ms

img_about03.png

img_about03.png

1018 ms

img_about04.png

img_about04.png

849 ms

img_about05.png

img_about05.png

851 ms

img_about06.png

img_about06.png

851 ms

txt_plans.png

txt_plans.png

859 ms

img_plans01.png

img_plans01.png

863 ms

img_plans02.png

img_plans02.png

1018 ms

img_plans03.png

img_plans03.png

1020 ms

img_section02_pc.png

img_section02_pc.png

1020 ms

txt_faq.png

txt_faq.png

1031 ms

img_faq.png

img_faq.png

1035 ms

img_quest01.png

img_quest01.png

1186 ms

img_quest02.png

img_quest02.png

1188 ms

img_quest03.png

img_quest03.png

1190 ms

img_quest04.png

img_quest04.png

1125 ms

gtm.js

gtm.js

60 ms

img_quest05.png

img_quest05.png

1060 ms

endpoint

endpoint

619 ms

106 ms

124 ms

box_started_top.png

box_started_top.png

1030 ms

box_started_bottom.png

box_started_bottom.png

1177 ms

box_started_in.png

box_started_in.png

1179 ms

txt_providing.png

txt_providing.png

1180 ms

img_started01.png

img_started01.png

1179 ms

conversion_async.js

conversion_async.js

37 ms

s_retargeting.js

s_retargeting.js

890 ms

conversion.js

conversion.js

1421 ms

img_started02.png

img_started02.png

1166 ms

42 ms

55 ms

63 ms

33 ms

22 ms

26 ms

img_started03.png

img_started03.png

1040 ms

mark_support_l.png

mark_support_l.png

1186 ms

mark_support_r.png

mark_support_r.png

1188 ms

ico_app_01_pc.png

ico_app_01_pc.png

1187 ms

s34653769764117

s34653769764117

81 ms

ico_facebook_01_pc.png

ico_facebook_01_pc.png

1025 ms

logo_03.png

logo_03.png

1039 ms

logo_mdb.png

logo_mdb.png

1041 ms

dmy_img_movie.png

dmy_img_movie.png

1349 ms

dmy_img_movie_pc.png

dmy_img_movie_pc.png

1360 ms

arw_pink_mdl_hover.png

arw_pink_mdl_hover.png

1022 ms

pagetop.png

pagetop.png

1023 ms

oct.js

oct.js

115 ms

adsct

adsct

100 ms

adsct

adsct

99 ms

adv.js

adv.js

28 ms

dg_gateway.js

dg_gateway.js

29 ms

adv_inner.js

adv_inner.js

4 ms

conversion.js

conversion.js

13 ms

15 ms

r.js

r.js

29 ms

15 ms

adv.aspx

adv.aspx

902 ms

23 ms

dgcore.js

dgcore.js

3 ms

adSiteVisit.js

adSiteVisit.js

4 ms

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

twincue.com

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: