Tools & Wizards About Us
curely.co screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

curely.co

Curely - Talk to doctors whenever, wherever

Page Load Speed

7.4 sec in total

First Response

613 ms

Resources Loaded

5.6 sec

Page Rendered

1.1 sec

curely.co screenshot

About Website

Visit curely.co now to see the best up-to-date Curely content for India and also check out these interesting facts you probably never knew about curely.co

Get multiple opinions for your symptoms, prescriptions, and diagnosis. It's like having a dream team of doctors from all over the world in every specialty.

Visit curely.co

Key Findings

We analyzed Curely.co page load time and found that the first response time was 613 ms and then it took 6.8 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

curely.co performance score

0

Network Requests Diagram

www.curely.co

613 ms

wp-emoji-release.min.js

249 ms

bootstrap_tab.min.css

184 ms

bootstrap_dropdown.min.css

185 ms

res_tab_icon.css

199 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 80% of them (61 requests) were addressed to the original Curely.co, 5% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Curely.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (16%)

Content Size

10.1 MB

After Optimization

8.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Curely.co main page is 10.1 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. Images take 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 135.3 kB

  • Original 176.0 kB
  • After minification 174.4 kB
  • After compression 40.7 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 135.3 kB or 77% of the original size.

Image Optimization

-8%

Potential reduce by 657.2 kB

  • Original 8.8 MB
  • After minification 8.1 MB

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. Curely images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 682.2 kB

  • Original 989.3 kB
  • After minification 971.1 kB
  • After compression 307.0 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 682.2 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 162.6 kB

  • Original 193.9 kB
  • After minification 159.2 kB
  • After compression 31.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. Curely.co needs all CSS files to be minified and compressed as it can save up to 162.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (48%)

Requests Now

71

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.curely.co

www.curely.co

613 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

249 ms

bootstrap_tab.min.css

bootstrap_tab.min.css

184 ms

bootstrap_dropdown.min.css

bootstrap_dropdown.min.css

185 ms

res_tab_icon.css

res_tab_icon.css

199 ms

prettyPhoto.css

prettyPhoto.css

301 ms

wp-video-lightbox.css

wp-video-lightbox.css

322 ms

front.css

front.css

357 ms

style.css

style.css

455 ms

font-awesome.css

font-awesome.css

441 ms

tablepress-combined.min.css

tablepress-combined.min.css

413 ms

jquery.js

jquery.js

676 ms

jquery-migrate.min.js

jquery-migrate.min.js

459 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

591 ms

video-lightbox.js

video-lightbox.js

575 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

686 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

709 ms

jquery.theme-main.min.js

jquery.theme-main.min.js

661 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

757 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

839 ms

curely.main.js

curely.main.js

820 ms

addthis_widget.js

addthis_widget.js

11 ms

output.css

output.css

771 ms

jquery.malihu.PageScroll2id.js

jquery.malihu.PageScroll2id.js

784 ms

jquery.malihu.PageScroll2id-init.js

jquery.malihu.PageScroll2id-init.js

803 ms

bootstrap-dropdown.js

bootstrap-dropdown.js

834 ms

bootstrap-tab.js

bootstrap-tab.js

921 ms

bootstrap-tabdrop.js

bootstrap-tabdrop.js

931 ms

wp-embed.min.js

wp-embed.min.js

969 ms

style.css

style.css

938 ms

jquery.bxslider.css

jquery.bxslider.css

654 ms

css

css

23 ms

css

css

36 ms

analytics.js

analytics.js

117 ms

fbds.js

fbds.js

91 ms

logo_horizontal_RGB.png

logo_horizontal_RGB.png

381 ms

header_bg3.png

header_bg3.png

1097 ms

header_bg2.png

header_bg2.png

1101 ms

header_bg1.png

header_bg1.png

1277 ms

play_btn.png

play_btn.png

256 ms

howitworks_img_1.png

howitworks_img_1.png

1471 ms

3_detail.png

3_detail.png

1201 ms

2_list.png

2_list.png

1798 ms

1_8categories.png

1_8categories.png

2475 ms

iphone_frame.png

iphone_frame.png

1901 ms

howitworks_02-2.png

howitworks_02-2.png

1378 ms

howitworks_img_2.png

howitworks_img_2.png

2123 ms

believe_01_img_mobile.png

believe_01_img_mobile.png

1663 ms

believe_01_img.png

believe_01_img.png

1758 ms

believe_02_img_mobile.png

believe_02_img_mobile.png

1819 ms

believe_02_img.png

believe_02_img.png

1943 ms

believe_03_img_mobile.png

believe_03_img_mobile.png

1971 ms

believe_03_img.png

believe_03_img.png

1987 ms

doctor_1_icon.png

doctor_1_icon.png

2068 ms

doctor_2_icon.png

doctor_2_icon.png

2109 ms

doctor_3_icon.png

doctor_3_icon.png

2141 ms

blog_bg.png

blog_bg.png

3084 ms

bottom_img.png

bottom_img.png

2939 ms

apple_store.png

apple_store.png

2282 ms

google_play_store.png

google_play_store.png

2291 ms

footer_bg.png

footer_bg.png

2980 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

167 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

170 ms

1TiHc9yag0wq3lDO9cw0vqCWcynf_cDxXwCLxiixG1c.ttf

1TiHc9yag0wq3lDO9cw0vqCWcynf_cDxXwCLxiixG1c.ttf

170 ms

TttUCfJ272GBgSKaOaD7KqCWcynf_cDxXwCLxiixG1c.ttf

TttUCfJ272GBgSKaOaD7KqCWcynf_cDxXwCLxiixG1c.ttf

170 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2581 ms

collect

collect

151 ms

279 ms

bx_loader.gif

bx_loader.gif

2245 ms

arrow_right.png

arrow_right.png

2404 ms

arrow_left.png

arrow_left.png

2440 ms

vantage-icons.woff

vantage-icons.woff

2546 ms

layers.e5ea973510bf60b3db41.js

layers.e5ea973510bf60b3db41.js

5 ms

300lo.json

300lo.json

47 ms

40 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

38 ms

SEO Factors

curely.co SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

curely.co

Open Graph data is detected on the main page of Curely. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: