4.9 sec in total
1.2 sec
3.5 sec
307 ms
Click here to check amazing Healthy Line content for United States. Otherwise, check out these important facts you probably never knew about healthyline.com
HealthyLine PEMF Technology Mats are the Only Mats that Combine both Far Infrared Ray and PEMF Therapies. 90 Days Money-Back Guarantee!
Visit healthyline.comWe analyzed Healthyline.com page load time and found that the first response time was 1.2 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
healthyline.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value7.6 s
3/100
25%
Value13.6 s
2/100
10%
Value9,350 ms
0/100
30%
Value0.001
100/100
15%
Value17.5 s
4/100
10%
1161 ms
186 ms
310 ms
11 ms
125 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 83% of them (104 requests) were addressed to the original Healthyline.com, 4% (5 requests) were made to Maps.google.com and 3% (4 requests) were made to Doctor-certified.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Healthyline.com.
Page size can be reduced by 1.7 MB (61%)
2.8 MB
1.1 MB
In fact, the total size of Healthyline.com main page is 2.8 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. 70% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 69.5 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 69.5 kB or 81% of the original size.
Potential reduce by 24.9 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. Healthy Line images are well optimized though.
Potential reduce by 1.1 MB
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.1 MB or 73% of the original size.
Potential reduce by 486.6 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. Healthyline.com needs all CSS files to be minified and compressed as it can save up to 486.6 kB or 84% of the original size.
Number of requests can be reduced by 107 (88%)
121
14
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Healthy Line. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 73 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
healthyline.com
1161 ms
wp-emoji-release.min.js
186 ms
gd_core_frontend.css
310 ms
font-awesome.min.css
11 ms
styles.css
125 ms
settings.css
193 ms
dynamic-captions.css
126 ms
static-captions.css
172 ms
prettyPhoto.css
189 ms
jquery.selectBox.css
192 ms
style.css
236 ms
font-awesome.min.css
247 ms
fonts.css
316 ms
style.css
437 ms
animate.css
380 ms
woocommerce.css
365 ms
supersized.css
314 ms
supersized.shutter.css
370 ms
jquery.bxslider.css
372 ms
prettyPhoto.css
431 ms
YTPlayer.css
423 ms
jquery.showcase.slider.css
429 ms
cloud-zoom.css
434 ms
responsive.css
496 ms
style.basic.css
486 ms
style-simple-red.css
490 ms
jquery.js
676 ms
jquery-migrate.min.js
495 ms
geodirectory.min.js
505 ms
js
32 ms
ajax-chosen.min.js
551 ms
jquery.themepunch.plugins.min.js
612 ms
jquery.themepunch.revolution.min.js
726 ms
twitterfetcher.js
559 ms
load.sumome.com
341 ms
asljquery.js
516 ms
jquery.gestures.js
626 ms
jquery.easing.js
517 ms
jquery.mousewheel.js
624 ms
get_webseal.js
274 ms
jquery.mCustomScrollbar.js
643 ms
jquery.ajaxsearchlite.js
670 ms
asl_wrapper.js
664 ms
jquery.form.min.js
618 ms
scripts.js
606 ms
jquery.lightbox-0.5.min.js
601 ms
goMap.min.js
602 ms
chosen.jquery.min.js
613 ms
core.min.js
569 ms
datepicker.min.js
560 ms
widget.min.js
555 ms
mouse.min.js
558 ms
slider.min.js
570 ms
effect.min.js
529 ms
effect-slide.min.js
530 ms
jquery.ui.timepicker.min.js
599 ms
jRating.jquery.min.js
589 ms
on_document_load.js
544 ms
geometa.min.js
540 ms
add-to-cart.min.js
542 ms
jquery.blockUI.min.js
543 ms
woocommerce.min.js
534 ms
css
57 ms
jquery.cookie.min.js
491 ms
cart-fragments.min.js
485 ms
jquery.prettyPhoto.min.js
514 ms
jquery.prettyPhoto.init.min.js
509 ms
jquery.selectBox.min.js
522 ms
analytics.js
12 ms
jquery.yith-wcwl.js
479 ms
jquery.easing.min.js
471 ms
collect
32 ms
collect
58 ms
supersized.3.2.7.js
419 ms
supersized.shutter.js
437 ms
jquery.nicescroll.min.js
555 ms
jquery.hoverIntent.minified.js
335 ms
jquery.bxslider.min.js
334 ms
fbds.js
238 ms
waypoints.min.js
315 ms
jquery.isotope.min.js
315 ms
jquery.infinitescroll.min.js
331 ms
imagesloaded.min.js
340 ms
jquery.stellar.min.js
340 ms
jquery.prettyPhoto.js
337 ms
jquery.videoBG.js
1276 ms
jquery.mb.YTPlayer.js
447 ms
jquery.modernizr.custom.js
399 ms
jquery.showcase.slider.js
393 ms
cloud-zoom.1.0.3.min.js
390 ms
feedback.js
225 ms
common.js
82 ms
util.js
81 ms
geocoder.js
79 ms
jquery.scrollTo.min.js
371 ms
jquery.localScroll.min.js
376 ms
jquery.placeholder.js
366 ms
functions.js
357 ms
main.js
398 ms
angelleye-frontend.js
399 ms
wp-embed.min.js
343 ms
PT_Sans-Caption-Web-Regular.ttf
649 ms
Judson-Regular.ttf
526 ms
top_overlay.png
388 ms
scroll-arrow.png
387 ms
left-side-bg.png
396 ms
healthyline150.png
447 ms
menu1_bg.png
446 ms
101 ms
search-icon.png
431 ms
s-icons.png
465 ms
V3A9763-344x430.jpg
581 ms
desc_title_bg.png
474 ms
desc_p_bg.png
518 ms
goodmorningxxlnew2.jpg
647 ms
Banner-2.jpg
772 ms
ajaxhandler.aspx
49 ms
ajax-loader1.gif
558 ms
favicon-new.png
32 ms
chat-bubbles.png
56 ms
index.php
134 ms
52 ms
13font.css
187 ms
seal_doctor2-blank.png
54 ms
popup_bg.png
64 ms
infowindow.js
4 ms
healthyline.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
healthyline.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
healthyline.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healthyline.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 Healthyline.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.
healthyline.com
Open Graph description is not detected on the main page of Healthy Line. 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: