Tools & Wizards About Us
frankieboyer.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

frankieboyer.com

Home

Page Load Speed

1.9 sec in total

First Response

309 ms

Resources Loaded

1.3 sec

Page Rendered

285 ms

frankieboyer.com screenshot

About Website

Visit frankieboyer.com now to see the best up-to-date Frankieboyer content and also check out these interesting facts you probably never knew about frankieboyer.com

Frankie Boyer Radio Shows Award Winning Talk Show Host Empowers Listeners To Live Healthy Vibrant Lives Get Our Groundbreaking Business & Health Tips [Form 7916] Holistic Talk RadioGroundbreaking ...

Visit frankieboyer.com

Key Findings

We analyzed Frankieboyer.com page load time and found that the first response time was 309 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

frankieboyer.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.412

24/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

home.html

309 ms

mm_css_menu.js

135 ms

contentlayout.css

207 ms

frankie_style.css

239 ms

logo.jpg

186 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 90% of them (19 requests) were addressed to the original Frankieboyer.com, 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (571 ms) belongs to the original domain Frankieboyer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.0 kB (18%)

Content Size

323.7 kB

After Optimization

266.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frankieboyer.com main page is 323.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 239.9 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 10.9 kB

  • Original 14.1 kB
  • After minification 13.3 kB
  • After compression 3.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 10.9 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 239.9 kB
  • After minification 239.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. Frankieboyer images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 33.4 kB

  • Original 54.9 kB
  • After minification 54.6 kB
  • After compression 21.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 33.4 kB or 61% of the original size.

CSS Optimization

-85%

Potential reduce by 12.7 kB

  • Original 14.9 kB
  • After minification 9.5 kB
  • After compression 2.2 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. Frankieboyer.com needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frankieboyer. According to our analytics all requests are already optimized.

Network Requests Diagram

home.html

home.html

309 ms

mm_css_menu.js

mm_css_menu.js

135 ms

contentlayout.css

contentlayout.css

207 ms

frankie_style.css

frankie_style.css

239 ms

logo.jpg

logo.jpg

186 ms

pic_spacer_fb.gif

pic_spacer_fb.gif

76 ms

spacer.gif

spacer.gif

175 ms

contentlayout_r1_c1.jpg

contentlayout_r1_c1.jpg

176 ms

contentlayout_r3_c2.jpg

contentlayout_r3_c2.jpg

177 ms

contentlayout_r5_c3.jpg

contentlayout_r5_c3.jpg

176 ms

contentlayout_r7_c5.jpg

contentlayout_r7_c5.jpg

185 ms

contentlayout_r9_c6.jpg

contentlayout_r9_c6.jpg

177 ms

analytics.js

analytics.js

7 ms

bg_blue.jpg

bg_blue.jpg

85 ms

homepage.jpg

homepage.jpg

571 ms

collect

collect

17 ms

contentlayout_r1_c1_f2.jpg

contentlayout_r1_c1_f2.jpg

76 ms

contentlayout_r3_c2_f2.jpg

contentlayout_r3_c2_f2.jpg

75 ms

contentlayout_r5_c3_f2.jpg

contentlayout_r5_c3_f2.jpg

87 ms

contentlayout_r7_c5_f2.jpg

contentlayout_r7_c5_f2.jpg

64 ms

contentlayout_r9_c6_f2.jpg

contentlayout_r9_c6_f2.jpg

62 ms

Accessibility Review

frankieboyer.com accessibility score

84

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

frankieboyer.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

frankieboyer.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frankieboyer.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Frankieboyer.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

frankieboyer.com

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