6.9 sec in total
689 ms
5.7 sec
583 ms
Welcome to lifewave.com homepage info - get ready to check Lifewave best content for United States right away, or after learning these important things about lifewave.com
LifeWave’s patented wellness products have helped people all over the world reach their greatest potential.
Visit lifewave.comWe analyzed Lifewave.com page load time and found that the first response time was 689 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lifewave.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value12.4 s
0/100
25%
Value10.9 s
6/100
10%
Value1,470 ms
14/100
30%
Value0.084
93/100
15%
Value19.6 s
2/100
10%
689 ms
1957 ms
20 ms
61 ms
474 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 44% of them (36 requests) were addressed to the original Lifewave.com, 31% (25 requests) were made to Cdn.sanity.io and 6% (5 requests) were made to App.five9.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Lifewave.com.
Page size can be reduced by 196.8 kB (16%)
1.2 MB
1.0 MB
In fact, the total size of Lifewave.com main page is 1.2 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. Images take 565.1 kB which makes up the majority of the site volume.
Potential reduce by 103.2 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 103.2 kB or 79% of the original size.
Potential reduce by 468 B
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. Lifewave images are well optimized though.
Potential reduce by 87.1 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 87.1 kB or 18% of the original size.
Potential reduce by 6.0 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. Lifewave.com needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 35% of the original size.
Number of requests can be reduced by 48 (67%)
72
24
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifewave. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
lifewave.com
689 ms
lifewave.com
1957 ms
swiper-bundle.min.js
20 ms
otSDKStub.js
61 ms
tailwindcss-output.css
474 ms
toastr.min.css
482 ms
bootstrap-modal.css
490 ms
swiper-bundle.min.css
21 ms
font-awesome.min.css
481 ms
globals.css
493 ms
pcModal.css
501 ms
router.min.js
650 ms
culture
681 ms
resource
1627 ms
require.min.js
689 ms
CustomerType.js
842 ms
Helpers.js
879 ms
googleAnalytics.js
886 ms
a254f4da-15cc-4bf2-aa51-dddd4606a069.json
24 ms
location
30 ms
otBannerSdk.js
19 ms
five9-social-widget.min.js
272 ms
gtm.js
84 ms
2b74cf3e7e6375a027cf2eee4f0aa4d48acf4907-5000x1224.jpg
392 ms
97cbce50df1816a47709f498f54b4b6076917921-5208x1275.jpg
395 ms
b0d7a6e7bcaabc8b07f46de2b7a20645b05a33d6-1440x469.jpg
346 ms
d19aa4b01b6e97c87af1929bd3b702b39984642b-1440x469.png
476 ms
98097398d1216a0c3a9263d0c17228cd9831564e-1440x469.jpg
257 ms
def25985d0be1f45caafe607d1c4edac8e66c474-91x91.svg
147 ms
fcaef30b5f61d5462340a3e1f5699dd9fb01531a-80x80.svg
258 ms
b6016ff535d671596cdb8747cd98e683eb4a03a6-90x90.svg
344 ms
11bb55ee7a170e9051eab9ac20de0749dd81aae0-80x80.svg
343 ms
cc533cb5c2f7a03ae789fc01f03e8a8780a2a1c0-90x90.svg
430 ms
198baa05ce692e83a454c30507a36fc409991cd5-80x80.svg
431 ms
a99b72b624b0c4aa0bf81d2eae4f43d2899e8570-90x90.svg
432 ms
32ac765f60ca91ef4457f41935a5c106647828c4-80x80.svg
473 ms
a5d95bb32e3c439a4ed7ce9ec92ccbdb1b84e66f-90x90.svg
480 ms
0c6f75a0fa585f95c7ded411f3f8a3cf8cc7a183-80x80.svg
514 ms
a487fbe6f8fa8a0fcd1ea0c242397a8dc361d6f4-90x90.svg
515 ms
26b9cab38025971877688053038e6d116e7a2aac-90x90.svg
517 ms
f5562f5cf53d8774028ae53d030d0db5982970b9-635x425.jpg
575 ms
a121d374b3eb2d7ba773178fc3ec4b1bf430c354-80x80.png
674 ms
e51616254c2282d001e59e6a5a5d146092d67f4f-80x80.png
575 ms
d9043fea327ae3fa2e0f78730ba6b65d6ada6e10-80x80.png
715 ms
e44046bbd2af7262c8a0c0337f86a0c5abec4eb5-80x80.svg
601 ms
cceaf79732a1ab1aceee1da4811e1b0d83a9fc06-85x85.svg
605 ms
88f19e91125b560bb088d866c1f75602fc50188b-85x85.svg
650 ms
c890697606e2215f81185b02f16d60e9a37e0a50-635x425.jpg
763 ms
left-arrow.svg
257 ms
right-arrow.svg
258 ms
extensions.js
240 ms
forms.js
316 ms
Montserrat-Light.ttf
399 ms
Montserrat-Regular.ttf
476 ms
Montserrat-Bold.ttf
393 ms
Gilmer-Regular.woff
438 ms
Gilmer-Light.woff
503 ms
Gilmer-Bold.woff
496 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
8 ms
jquery-3.7.1.min.js
530 ms
cookies.js
532 ms
ajax.js
793 ms
toastr.min.js
801 ms
app.js
831 ms
pubsub.js
822 ms
otSDKStub.js
22 ms
js
49 ms
detector-dom.min.js
24 ms
five9-social-widget.css
105 ms
config.js
15 ms
detector-bootstrap_es5.min.js
70 ms
chat-small.png
81 ms
app.js
117 ms
minus-32.png
72 ms
external-link-32.png
141 ms
jquery.validate.min.js
712 ms
bootstrap.min.js
276 ms
jquery-migrate-3.4.1.min.js
665 ms
jquery.unobtrusive-ajax.js
591 ms
jquery.validate.unobtrusive.min.js
282 ms
nr-spa-1216.min.js
16 ms
lifewave.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
lifewave.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lifewave.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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Lifewave.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 Lifewave.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.
lifewave.com
Open Graph description is not detected on the main page of Lifewave. 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: