Tools & Wizards About Us
heartwisemag.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

heartwisemag.com

Healthy and Heartwise | Magazine

Page Load Speed

14.2 sec in total

First Response

6.6 sec

Resources Loaded

7.4 sec

Page Rendered

221 ms

heartwisemag.com screenshot

About Website

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

Visit heartwisemag.com

Key Findings

We analyzed Heartwisemag.com page load time and found that the first response time was 6.6 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

heartwisemag.com performance score

0

Network Requests Diagram

heartwisemag.com

6620 ms

wp-emoji-release.min.js

189 ms

css

29 ms

css

40 ms

public.css

126 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 46% of them (26 requests) were addressed to the original Heartwisemag.com, 12% (7 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Heartwisemag.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 993.3 kB (71%)

Content Size

1.4 MB

After Optimization

399.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heartwisemag.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. 60% of websites need less resources to load. Javascripts take 679.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 98.9 kB

  • Original 113.8 kB
  • After minification 101.2 kB
  • After compression 14.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 12.6 kB, which is 11% 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 98.9 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 3.5 kB

  • Original 76.0 kB
  • After minification 72.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. Heartwise Mag images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 449.1 kB

  • Original 679.7 kB
  • After minification 562.4 kB
  • After compression 230.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 449.1 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 441.8 kB

  • Original 523.3 kB
  • After minification 393.9 kB
  • After compression 81.5 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. Heartwisemag.com needs all CSS files to be minified and compressed as it can save up to 441.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (57%)

Requests Now

46

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heartwisemag.com

heartwisemag.com

6620 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

189 ms

css

css

29 ms

css

css

40 ms

public.css

public.css

126 ms

js_composer.css

js_composer.css

590 ms

style.css

style.css

558 ms

dashicons.min.css

dashicons.min.css

249 ms

thickbox.css

thickbox.css

192 ms

baze_styles_youtube.css

baze_styles_youtube.css

253 ms

jquery.js

jquery.js

440 ms

jquery-migrate.min.js

jquery-migrate.min.js

314 ms

youtube_embed_front_end.js

youtube_embed_front_end.js

336 ms

iframe_api

iframe_api

43 ms

zedity-reset.css

zedity-reset.css

378 ms

adsbygoogle.js

adsbygoogle.js

8 ms

widget.js

widget.js

64 ms

tagdiv_theme.js

tagdiv_theme.js

350 ms

comment-reply.min.js

comment-reply.min.js

74 ms

thickbox.js

thickbox.js

95 ms

js_composer_front.js

js_composer_front.js

199 ms

zedity-responsive.min.js

zedity-responsive.min.js

155 ms

widget.js

widget.js

96 ms

www-widgetapi.js

www-widgetapi.js

59 ms

ga.js

ga.js

28 ms

fbds.js

fbds.js

26 ms

analytics.js

analytics.js

57 ms

925117ce02ca9d8471026ab9ae07aa35

925117ce02ca9d8471026ab9ae07aa35

103 ms

heartwisepicturesandlogos-0015-300x202.jpg

heartwisepicturesandlogos-0015-300x202.jpg

102 ms

newsmag-mobile.png

newsmag-mobile.png

102 ms

DIET-DVD-1-Cholesterol-300x160.jpg

DIET-DVD-1-Cholesterol-300x160.jpg

102 ms

ico-video-large.png

ico-video-large.png

102 ms

DIET-DVD-2-Weight-Loss-300x160.jpg

DIET-DVD-2-Weight-Loss-300x160.jpg

101 ms

heartwisepicturesandlogos-0011-300x202.jpg

heartwisepicturesandlogos-0011-300x202.jpg

158 ms

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

45 ms

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

73 ms

IgZJs4-7SA1XX_edsoXWog.ttf

IgZJs4-7SA1XX_edsoXWog.ttf

133 ms

DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf

DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf

148 ms

newsmag.svg

newsmag.svg

221 ms

newsmag.woff

newsmag.woff

175 ms

Zd2E9abXLFGSr9G3YK2MsKDbm6fPDOZJsR8PmdG62gY.ttf

Zd2E9abXLFGSr9G3YK2MsKDbm6fPDOZJsR8PmdG62gY.ttf

132 ms

b9QBgL0iMZfDSpmcXcE8nJRhFVcex_hajThhFkHyhYk.ttf

b9QBgL0iMZfDSpmcXcE8nJRhFVcex_hajThhFkHyhYk.ttf

147 ms

b9QBgL0iMZfDSpmcXcE8nPOYkGiSOYDq_T7HbIOV1hA.ttf

b9QBgL0iMZfDSpmcXcE8nPOYkGiSOYDq_T7HbIOV1hA.ttf

147 ms

ca-pub-4916802390674282.js

ca-pub-4916802390674282.js

201 ms

zrt_lookup.html

zrt_lookup.html

141 ms

show_ads_impl.js

show_ads_impl.js

88 ms

132 ms

__utm.gif

__utm.gif

49 ms

collect

collect

147 ms

ads

ads

49 ms

collect

collect

104 ms

osd.js

osd.js

60 ms

ads

ads

45 ms

ads

ads

116 ms

widget

widget

194 ms

loadingAnimation.gif

loadingAnimation.gif

65 ms

19 ms

SEO Factors

heartwisemag.com 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 Heartwisemag.com 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 Heartwisemag.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

heartwisemag.com

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