Tools & Wizards About Us
rogerlove.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

rogerlove.com

Home - Roger Love

Page Load Speed

4 sec in total

First Response

56 ms

Resources Loaded

3.5 sec

Page Rendered

509 ms

rogerlove.com screenshot

About Website

Click here to check amazing Roger Love content for United States. Otherwise, check out these important facts you probably never knew about rogerlove.com

Visit rogerlove.com

Key Findings

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

Performance Metrics

rogerlove.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value3,070 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

rogerlove.com

56 ms

rogerlove.com

261 ms

cv.css

41 ms

cvpro.min.css

46 ms

prettyPhoto.css

54 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 52% of them (65 requests) were addressed to the original Rogerlove.com, 11% (14 requests) were made to Fonts.gstatic.com and 7% (9 requests) were made to Iheart.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Americancornhole.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.4 kB (12%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rogerlove.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. 80% 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 86.0 kB

  • Original 106.4 kB
  • After minification 101.7 kB
  • After compression 20.3 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 86.0 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 182.0 kB

  • Original 1.8 MB
  • After minification 1.6 MB

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. Roger Love images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 45.7 kB

  • Original 703.1 kB
  • After minification 702.8 kB
  • After compression 657.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 19.7 kB

  • Original 273.8 kB
  • After minification 273.8 kB
  • After compression 254.1 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 78 (78%)

Requests Now

100

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 100 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 52 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

rogerlove.com

rogerlove.com

56 ms

rogerlove.com

rogerlove.com

261 ms

cv.css

cv.css

41 ms

cvpro.min.css

cvpro.min.css

46 ms

prettyPhoto.css

prettyPhoto.css

54 ms

wp-video-lightbox.css

wp-video-lightbox.css

51 ms

font-awesome.min.css

font-awesome.min.css

51 ms

css

css

57 ms

frontend.css

frontend.css

31 ms

menu-image.css

menu-image.css

53 ms

dashicons.min.css

dashicons.min.css

54 ms

1-popupally-pro-style.css

1-popupally-pro-style.css

59 ms

style.css

style.css

57 ms

close-button-icon.css

close-button-icon.css

258 ms

YouTubePopUp.css

YouTubePopUp.css

217 ms

boxed.css

boxed.css

60 ms

font-awesome.min.css

font-awesome.min.css

63 ms

grid-system.css

grid-system.css

68 ms

style.css

style.css

94 ms

header-secondary-nav.css

header-secondary-nav.css

72 ms

magnific.css

magnific.css

79 ms

css

css

52 ms

responsive.css

responsive.css

82 ms

ascend.css

ascend.css

87 ms

js_composer.min.css

js_composer.min.css

117 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

122 ms

css

css

50 ms

jquery.min.js

jquery.min.js

127 ms

jquery-migrate.min.js

jquery-migrate.min.js

128 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

127 ms

video-lightbox.js

video-lightbox.js

128 ms

check-source.min.js

check-source.min.js

129 ms

1-popupally-pro-code.js

1-popupally-pro-code.js

129 ms

popup.min.js

popup.min.js

129 ms

YouTubePopUp.jquery.js

YouTubePopUp.jquery.js

279 ms

YouTubePopUp.js

YouTubePopUp.js

348 ms

js

js

66 ms

fusedesk-ajax.js

fusedesk-ajax.js

141 ms

267e2b2d-3e85-495d-b1d5-8da9307ffea8.js

267e2b2d-3e85-495d-b1d5-8da9307ffea8.js

80 ms

embed.js

embed.js

318 ms

email-decode.min.js

email-decode.min.js

115 ms

cv.js

cv.js

129 ms

cvpro.min.js

cvpro.min.js

138 ms

frontend.js

frontend.js

142 ms

salient-social.js

salient-social.js

160 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

155 ms

jquery.easing.js

jquery.easing.js

170 ms

jquery.mousewheel.js

jquery.mousewheel.js

162 ms

priority.js

priority.js

176 ms

transit.js

transit.js

177 ms

waypoints.js

waypoints.js

179 ms

imagesLoaded.min.js

imagesLoaded.min.js

184 ms

hoverintent.js

hoverintent.js

191 ms

magnific.js

magnific.js

191 ms

superfish.js

superfish.js

195 ms

init.js

init.js

230 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

212 ms

isotope.min.js

isotope.min.js

211 ms

nectar-blog.js

nectar-blog.js

204 ms

touchswipe.min.js

touchswipe.min.js

200 ms

js_composer_front.min.js

js_composer_front.min.js

198 ms

gtm.js

gtm.js

66 ms

gtm.js

gtm.js

171 ms

fbevents.js

fbevents.js

88 ms

transparent1.png

transparent1.png

828 ms

logo6-1.png

logo6-1.png

59 ms

index-cta-2a-freeTraining.png

index-cta-2a-freeTraining.png

691 ms

index-cta-2b-freeTrainig.png

index-cta-2b-freeTrainig.png

58 ms

image-05.jpg

image-05.jpg

690 ms

VoicemailChallenge.png

VoicemailChallenge.png

121 ms

blog-header-storytelling-2-1024x425.png

blog-header-storytelling-2-1024x425.png

60 ms

blog-header-speak-in-tune-1024x425.png

blog-header-speak-in-tune-1024x425.png

163 ms

index-03-mobile.jpg

index-03-mobile.jpg

1033 ms

index-03.jpg

index-03.jpg

1048 ms

index-video1.jpg

index-video1.jpg

849 ms

index-video2.jpg

index-video2.jpg

1005 ms

index-video3.jpg

index-video3.jpg

1004 ms

index-header.jpg

index-header.jpg

1012 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

145 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

160 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

186 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

227 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

214 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

74 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

74 ms

SFProDisplay-Bold.woff

SFProDisplay-Bold.woff

2162 ms

SFProDisplay-Black.woff

SFProDisplay-Black.woff

2717 ms

SFProDisplay-Semibold.woff

SFProDisplay-Semibold.woff

1909 ms

SFProDisplay-Regular.woff

SFProDisplay-Regular.woff

2024 ms

SFProDisplay-Ultralight.woff

SFProDisplay-Ultralight.woff

2113 ms

243 ms

background-red-wide.jpg

background-red-wide.jpg

74 ms

css

css

72 ms

form_embed-70ab594381937fc46cadbbaab29c12b724dc077086662f2bbd495c08e46bb08d.css

form_embed-70ab594381937fc46cadbbaab29c12b724dc077086662f2bbd495c08e46bb08d.css

115 ms

form_embed-fd7a5360fe56f0a332f934492d89f18c2202d65871804504adca6fd4b6e78ceb.js

form_embed-fd7a5360fe56f0a332f934492d89f18c2202d65871804504adca6fd4b6e78ceb.js

142 ms

api.js

api.js

113 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

81 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

39 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

376 ms

aHR0cHM6Ly9kM3dvNXdvanZ1djdsLmNsb3VkZnJvbnQubmV0L3RfcnNzX2l0dW5lc19zcXVhcmVfMTQwMC9pbWFnZXMuc3ByZWFrZXIuY29tL29yaWdpbmFsL2ViNjViYjdiNjY4ZmMwZWZkYmVkM2NjMjhlNzZkMDY1LmpwZw

aHR0cHM6Ly9kM3dvNXdvanZ1djdsLmNsb3VkZnJvbnQubmV0L3RfcnNzX2l0dW5lc19zcXVhcmVfMTQwMC9pbWFnZXMuc3ByZWFrZXIuY29tL29yaWdpbmFsL2ViNjViYjdiNjY4ZmMwZWZkYmVkM2NjMjhlNzZkMDY1LmpwZw

627 ms

runtime.widget.js

runtime.widget.js

412 ms

401.widget.js

401.widget.js

676 ms

641.widget.js

641.widget.js

413 ms

604.widget.js

604.widget.js

677 ms

931.widget.js

931.widget.js

413 ms

234.widget.js

234.widget.js

447 ms

694.widget.js

694.widget.js

447 ms

podcastProfile.widget.js

podcastProfile.widget.js

455 ms

recaptcha__en.js

recaptcha__en.js

456 ms

icomoon.woff

icomoon.woff

345 ms

anchor

anchor

40 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

13 ms

UebCYnqdbF9ngI7DuCagEaT4xpR4mAb5pwZcsRDRe9I.js

UebCYnqdbF9ngI7DuCagEaT4xpR4mAb5pwZcsRDRe9I.js

44 ms

webworker.js

webworker.js

40 ms

logo_48.png

logo_48.png

29 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

32 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

33 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

32 ms

recaptcha__en.js

recaptcha__en.js

33 ms

Accessibility Review

rogerlove.com accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

rogerlove.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rogerlove.com SEO score

70

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 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.

Social Sharing Optimization

rogerlove.com

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