Tools & Wizards About Us
intimateconnexion.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

2.7 sec in total

First Response

761 ms

Resources Loaded

1.9 sec

Page Rendered

85 ms

intimateconnexion.com screenshot

About Website

Visit intimateconnexion.com now to see the best up-to-date Intimate Connexion content for United States and also check out these interesting facts you probably never knew about intimateconnexion.com

Visit intimateconnexion.com

Key Findings

We analyzed Intimateconnexion.com page load time and found that the first response time was 761 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

intimateconnexion.com performance score

0

Network Requests Diagram

intimateconnexion.com

761 ms

jquery-1.9.1.js

94 ms

index_page.css

45 ms

selectbox.css

37 ms

jquery.formstyler.css

47 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 97% of them (69 requests) were addressed to the original Intimateconnexion.com, 1% (1 request) were made to Connect.facebook.net and 1% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (919 ms) belongs to the original domain Intimateconnexion.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (71%)

Content Size

2.4 MB

After Optimization

688.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intimateconnexion.com main page is 2.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. 55% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 31.7 kB

  • Original 40.7 kB
  • After minification 35.9 kB
  • After compression 8.9 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.8 kB, which is 12% 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 31.7 kB or 78% of the original size.

Image Optimization

-13%

Potential reduce by 56.8 kB

  • Original 427.4 kB
  • After minification 370.6 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. Obviously, Intimate Connexion needs image optimization as it can save up to 56.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-84%

Potential reduce by 1.5 MB

  • Original 1.8 MB
  • After minification 1.1 MB
  • After compression 284.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 1.5 MB or 84% of the original size.

CSS Optimization

-79%

Potential reduce by 91.9 kB

  • Original 116.3 kB
  • After minification 95.6 kB
  • After compression 24.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. Intimateconnexion.com needs all CSS files to be minified and compressed as it can save up to 91.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (73%)

Requests Now

70

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intimateconnexion.com

intimateconnexion.com

761 ms

jquery-1.9.1.js

jquery-1.9.1.js

94 ms

index_page.css

index_page.css

45 ms

selectbox.css

selectbox.css

37 ms

jquery.formstyler.css

jquery.formstyler.css

47 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

63 ms

modernizr.js

modernizr.js

60 ms

prettyCheckable.js

prettyCheckable.js

53 ms

jquery-ui-1.10.3.js

jquery-ui-1.10.3.js

129 ms

script.js

script.js

90 ms

jquery.popup.js

jquery.popup.js

59 ms

jquery.scrollTo.js

jquery.scrollTo.js

66 ms

jquery.autosize.js

jquery.autosize.js

113 ms

jquery.form.js

jquery.form.js

119 ms

lib.js

lib.js

120 ms

selectbox.js

selectbox.js

110 ms

jquery.formstyler.js

jquery.formstyler.js

114 ms

jquery.location.js

jquery.location.js

112 ms

login_form.js

login_form.js

117 ms

profile_photo.js

profile_photo.js

152 ms

messages.js

messages.js

149 ms

jquery.lazyload.js

jquery.lazyload.js

150 ms

server.js

server.js

122 ms

soundmanager2-nodebug-jsmin.js

soundmanager2-nodebug-jsmin.js

157 ms

jquery.winFocus.js

jquery.winFocus.js

148 ms

jquery.highlight.js

jquery.highlight.js

149 ms

users_rated_me.js

users_rated_me.js

150 ms

rate_people_photo.js

rate_people_photo.js

150 ms

gifts.js

gifts.js

149 ms

device.min.js

device.min.js

154 ms

video-js.css

video-js.css

154 ms

videojs-ie8.min.js

videojs-ie8.min.js

155 ms

videojs.css

videojs.css

153 ms

css.php

css.php

880 ms

js.php

js.php

919 ms

index_animated.css

index_animated.css

168 ms

video.js

video.js

241 ms

lazy_loader.gif

lazy_loader.gif

38 ms

lazy_loader_black.gif

lazy_loader_black.gif

35 ms

pp_small_decor_r.png

pp_small_decor_r.png

130 ms

alert_decor_question.png

alert_decor_question.png

35 ms

alert_decor_error.png

alert_decor_error.png

35 ms

empty.png

empty.png

130 ms

icon_close_grey.png

icon_close_grey.png

36 ms

icon_close_grey_hover.png

icon_close_grey_hover.png

129 ms

pp_small_decor_r_profile.png

pp_small_decor_r_profile.png

126 ms

pp_small_list_marker.png

pp_small_list_marker.png

127 ms

button_video_chat-hover.png

button_video_chat-hover.png

127 ms

main_urban.png

main_urban.png

131 ms

main_urban_footer.png

main_urban_footer.png

130 ms

lazy_loader_green.gif

lazy_loader_green.gif

129 ms

sdk.js

sdk.js

23 ms

lang_marker.png

lang_marker.png

105 ms

icons.png

icons.png

105 ms

facebook.png

facebook.png

108 ms

google-plus.png

google-plus.png

107 ms

linkedin.png

linkedin.png

105 ms

twitter.png

twitter.png

107 ms

vk.png

vk.png

106 ms

frm_login_bg.png

frm_login_bg.png

107 ms

frm_login_foot_bg.png

frm_login_foot_bg.png

107 ms

btns.png

btns.png

110 ms

frm_login_shadow.png

frm_login_shadow.png

107 ms

empty.gif

empty.gif

107 ms

vertical_dot.png

vertical_dot.png

109 ms

icon_footer.png

icon_footer.png

108 ms

marker_footer_nav.gif

marker_footer_nav.gif

105 ms

urban_footer_image_20.png

urban_footer_image_20.png

106 ms

page_shadow.png

page_shadow.png

108 ms

analytics.js

analytics.js

108 ms

urban_main_page_image_113.jpg

urban_main_page_image_113.jpg

34 ms

SEO Factors

intimateconnexion.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intimateconnexion.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Intimateconnexion.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

intimateconnexion.com

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