5.2 sec in total
242 ms
4.7 sec
200 ms
Visit rawlife.org now to see the best up-to-date Raw Life content and also check out these interesting facts you probably never knew about rawlife.org
A Day In The Life Of Raw Alignment! Hi there beautiful people! Thanks so much for watching this video! I hope that you enjoyed this little sneak peek into my li
Visit rawlife.orgWe analyzed Rawlife.org page load time and found that the first response time was 242 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
rawlife.org performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value11.7 s
0/100
25%
Value9.7 s
10/100
10%
Value160 ms
93/100
30%
Value0.002
100/100
15%
Value13.6 s
11/100
10%
242 ms
339 ms
2263 ms
250 ms
178 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Rawlife.org, 13% (10 requests) were made to I.ytimg.com and 9% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Wn.com.
Page size can be reduced by 730.3 kB (38%)
1.9 MB
1.2 MB
In fact, the total size of Rawlife.org main page is 1.9 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 987.9 kB which makes up the majority of the site volume.
Potential reduce by 336.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. 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 336.9 kB or 83% of the original size.
Potential reduce by 35.5 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. Raw Life images are well optimized though.
Potential reduce by 357.2 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 357.2 kB or 36% of the original size.
Potential reduce by 823 B
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. Rawlife.org has all CSS files already compressed.
Number of requests can be reduced by 23 (37%)
63
40
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raw Life. 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 6 to 1 for CSS and as a result speed up the page load time.
rawlife.org
242 ms
rawlife.org
339 ms
Raw_life
2263 ms
f10fd2cbad84386e125817a309cd00.js
250 ms
561e4cc9554755b1f21853e2be9e47.css
178 ms
font-awesome.min.css
187 ms
videoplayer-20181002-4.min.js
174 ms
api.js
37 ms
fMXW9rrR6xmp
431 ms
mw.css
185 ms
jquery.touchtoclick.js
162 ms
ga.js
52 ms
logo.png
257 ms
Raw01-ac78bc.jpg
547 ms
0.jpg
80 ms
459acaeef410935980acaa75614c-medium.jpg
35 ms
cf8fefc36b84a0749734720a39b5-medium.jpg
36 ms
97ec852f7c57a62bf4a9a01702d9-medium.jpg
264 ms
search-button.png
258 ms
logo.png
258 ms
a9fe7381387f49dcf5c1ed594f0f-medium.jpg
72 ms
0.jpg
90 ms
0.jpg
119 ms
0.jpg
118 ms
0.jpg
180 ms
0.jpg
124 ms
0.jpg
181 ms
0.jpg
124 ms
0.jpg
181 ms
0.jpg
179 ms
Hopsin-Raw-0828ce.jpg
489 ms
Ra-raw-2006-b8dbec.jpg
490 ms
Slyfamstone-life-ca850c.jpg
491 ms
Lmcc-000599.png
564 ms
Our_Lady_Peace_-_Life-e3a0b2.jpg
569 ms
recaptcha__en.js
122 ms
sdk.js
75 ms
505 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
71 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
105 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
111 ms
fontawesome-webfont.woff
111 ms
__utm.gif
24 ms
__utm.gif
17 ms
sdk.js
10 ms
ga-audiences
72 ms
iconSprite.png
29 ms
iframe_api
212 ms
modal-gloss.png
375 ms
wn_logo.png
339 ms
lftracker_v1_p1e024BnDD64GB6d.js
153 ms
quant.js
143 ms
__utm.gif
114 ms
iconSprite01.png
115 ms
playPrev-button.png
39 ms
playNext-button.png
38 ms
fallback
30 ms
rules-p-69LMgINxZpq8g.js
75 ms
fallback__ltr.css
15 ms
www-widgetapi.js
14 ms
tr-rc.lfeeder.com
94 ms
css
75 ms
KieI76KGWro
100 ms
pixel;r=2045764647;labels=wn.anything.main;rf=0;a=p-69LMgINxZpq8g;url=https%3A%2F%2Fwn.com%2FRaw_life%2Fnews;uht=2;fpan=0;fpa=P0-1070761041-1714940755550;pbc=;ns=0;ce=1;qjs=1;qv=b70d35e8-20231208114759;cm=;gdpr=0;ref=;d=wn.com;dst=0;et=1715548875298;tzo=-180;ogl=title.Raw%20life%2Curl.https%3A%2F%2Fwn%252Ecom%2FRaw_Life%2Cimage.https%3A%2F%2Fi%252Eytimg%252Ecom%2Fvi%2FKieI76KGWro%2F0%252Ejpg%2Csite_name.World%20News%2Cvideo.http%3A%2F%2Fwww%252Eyoutube-nocookie%252Ecom%2Fv%2FKieI76KGWro%2Cvideo%3Aheight.240%2Cvideo%3Awidth.320%2Cvideo%3Atype.application%2Fx-shockwave-flash;ses=a0f9b8e7-4537-4432-9ef8-48237877ed3c;mdl=
28 ms
logo_48.png
3 ms
www-player.css
6 ms
www-embed-player.js
34 ms
base.js
62 ms
ad_status.js
197 ms
qpyvZYiO2MAIFFZ1w1cPPnd-o4I1izwn5tcH8iv7L0M.js
136 ms
embed.js
77 ms
KFOmCnqEu92Fr1Mu4mxM.woff
29 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
38 ms
KFOmCnqEu92Fr1Mu4mxM.woff
23 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
23 ms
rawlife.org accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
rawlife.org 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
Browser errors were logged to the console
Page has valid source maps
rawlife.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Rawlife.org 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 Rawlife.org 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.
rawlife.org
Open Graph description is not detected on the main page of Raw Life. 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: