4.2 sec in total
255 ms
3.2 sec
753 ms
Click here to check amazing Roger Love content for United States. Otherwise, check out these important facts you probably never knew about rogerlove.com
Improve your speech and singing voice with Roger Love's online voice & singing training program. Get the voice you want and need for success!
Visit rogerlove.comWe analyzed Rogerlove.com page load time and found that the first response time was 255 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
rogerlove.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value12.2 s
0/100
25%
Value9.5 s
11/100
10%
Value2,980 ms
3/100
30%
Value0.109
87/100
15%
Value31.3 s
0/100
10%
255 ms
42 ms
62 ms
47 ms
55 ms
Our browser made a total of 131 requests to load all elements on the main page. We found that 44% of them (57 requests) were addressed to the original Rogerlove.com, 11% (14 requests) were made to Fonts.gstatic.com and 8% (10 requests) were made to Iheart.com. The less responsive or slowest element that took the longest time to load (807 ms) belongs to the original domain Rogerlove.com.
Page size can be reduced by 812.1 kB (24%)
3.3 MB
2.5 MB
In fact, the total size of Rogerlove.com main page is 3.3 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 111.6 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 111.6 kB or 81% of the original size.
Potential reduce by 286.7 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. Obviously, Roger Love needs image optimization as it can save up to 286.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 76.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 76.2 kB or 22% of the original size.
Potential reduce by 337.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. Rogerlove.com needs all CSS files to be minified and compressed as it can save up to 337.5 kB or 58% of the original size.
Number of requests can be reduced by 82 (73%)
112
30
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Roger Love. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
rogerlove.com
255 ms
prettyPhoto.css
42 ms
wp-video-lightbox.css
62 ms
font-awesome.min.css
47 ms
css
55 ms
menu-image.css
58 ms
dashicons.min.css
56 ms
style.css
105 ms
close-button-icon.css
284 ms
YouTubePopUp.css
300 ms
style.css
74 ms
boxed.css
86 ms
font-awesome.min.css
98 ms
grid-system.css
107 ms
style.css
117 ms
header-secondary-nav.css
165 ms
magnific.css
166 ms
css
57 ms
responsive.css
168 ms
style.css
166 ms
ascend.css
184 ms
js_composer.min.css
175 ms
pum-site-styles.css
189 ms
salient-dynamic-styles.css
192 ms
css
65 ms
jquery.min.js
202 ms
jquery-migrate.min.js
204 ms
jquery.prettyPhoto.js
210 ms
video-lightbox.js
213 ms
YouTubePopUp.jquery.js
214 ms
YouTubePopUp.js
444 ms
js
68 ms
js
141 ms
5f25978440a633bf848fcbad606f4c2c.js
477 ms
embed.js
160 ms
email-decode.min.js
266 ms
getTrackingCode
15 ms
salient-social.js
203 ms
gtm4wp-form-move-tracker.js
216 ms
jquery.easing.js
226 ms
jquery.mousewheel.js
243 ms
priority.js
266 ms
transit.js
270 ms
waypoints.js
368 ms
imagesLoaded.min.js
660 ms
hoverintent.js
316 ms
magnific.js
305 ms
superfish.js
291 ms
init.js
290 ms
isotope.min.js
290 ms
nectar-blog.js
275 ms
touchswipe.min.js
267 ms
core.min.js
250 ms
pum-site-scripts.js
246 ms
js_composer_front.min.js
249 ms
css
24 ms
gtm.js
74 ms
gtm.js
106 ms
fbevents.js
106 ms
analytics.js
189 ms
conversion_async.js
178 ms
transparent1.png
287 ms
logo.png
39 ms
index-cta-2a.png
102 ms
index-cta-2b-1.png
169 ms
image-05.jpg
37 ms
blog-header-warmup1-1024x425.png
163 ms
blog-header-stage-1024x425.png
166 ms
blog-header-listen2-1024x425.png
164 ms
index-03-mobile.jpg
652 ms
index-03.jpg
653 ms
index-video1.jpg
436 ms
index-video2.jpg
438 ms
index-video3.jpg
435 ms
index-header.jpg
556 ms
1539971276241376
138 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
140 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
290 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
321 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
343 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
369 ms
ieVl2ZhZI2eCN5jzbjEETS9weq8-19K7CA.ttf
319 ms
fontawesome-webfont.svg
137 ms
fontawesome-webfont.woff
118 ms
ec.js
102 ms
collect
238 ms
436 ms
322 ms
background-red-wide.jpg
807 ms
css
166 ms
form_embed-ecdf08b1749d79682c2ab0463956d0c0ab955b29591a56ed173594b870d4dfb7.css
296 ms
form_embed-fd7a5360fe56f0a332f934492d89f18c2202d65871804504adca6fd4b6e78ceb.js
377 ms
api.js
176 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
206 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
254 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
275 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
255 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
275 ms
collect
107 ms
collect
106 ms
fontawesome-webfont.woff
106 ms
collect
611 ms
collect
643 ms
aHR0cHM6Ly9kM3dvNXdvanZ1djdsLmNsb3VkZnJvbnQubmV0L3RfcnNzX2l0dW5lc19zcXVhcmVfMTQwMC9pbWFnZXMuc3ByZWFrZXIuY29tL29yaWdpbmFsL2ViNjViYjdiNjY4ZmMwZWZkYmVkM2NjMjhlNzZkMDY1LmpwZw
785 ms
runtime.widget.js
112 ms
773.widget.js
498 ms
479.widget.js
498 ms
258.widget.js
597 ms
31.widget.js
500 ms
427.widget.js
604 ms
706.widget.js
596 ms
388.widget.js
603 ms
podcastProfile.widget.js
603 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
398 ms
492 ms
recaptcha__en.js
575 ms
icomoon.woff
432 ms
S9KxqRUcnCU
609 ms
ga-audiences
186 ms
ga-audiences
175 ms
www-player.css
54 ms
www-embed-player.js
109 ms
base.js
163 ms
fetch-polyfill.js
108 ms
ad_status.js
279 ms
id
247 ms
0Q0sPaTf27KkVV0qBrYI7cmJeSJkpG4CF1zVddAZEjs.js
116 ms
embed.js
10 ms
widget.js
185 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
127 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
128 ms
rogerlove.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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
rogerlove.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
Missing source maps for large first-party JavaScript
rogerlove.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rogerlove.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 Rogerlove.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.
rogerlove.com
Open Graph data is detected on the main page of Roger Love. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: