Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

community.capradio.org

Donate to CapRadio

Page Load Speed

4.7 sec in total

First Response

138 ms

Resources Loaded

3.8 sec

Page Rendered

751 ms

community.capradio.org screenshot

About Website

Click here to check amazing Community Cap Radio content for United States. Otherwise, check out these important facts you probably never knew about community.capradio.org

Visit community.capradio.org

Key Findings

We analyzed Community.capradio.org page load time and found that the first response time was 138 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

community.capradio.org performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.447

20/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

community.capradio.org

138 ms

community.capradio.org

481 ms

stylesheet0.635668342545870000.css

1599 ms

stylesheet8.635782063326670000.css

2435 ms

IE8Menu.css

2607 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 89% of them (42 requests) were addressed to the original Community.capradio.org, 4% (2 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Community.capradio.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 359.6 kB (19%)

Content Size

1.9 MB

After Optimization

1.5 MB

In fact, the total size of Community.capradio.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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 43.1 kB

  • Original 57.1 kB
  • After minification 54.3 kB
  • After compression 14.0 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 43.1 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 99.9 kB

  • Original 1.5 MB
  • After minification 1.4 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. Community Cap Radio images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 216.4 kB

  • Original 304.1 kB
  • After minification 264.9 kB
  • After compression 87.7 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 216.4 kB or 71% of the original size.

CSS Optimization

-88%

Potential reduce by 176 B

  • Original 199 B
  • After minification 23 B
  • After compression 23 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. Community.capradio.org needs all CSS files to be minified and compressed as it can save up to 176 B or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (27%)

Requests Now

44

After Optimization

32

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Cap Radio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

community.capradio.org accessibility score

67

Accessibility Issues

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

community.capradio.org 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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

community.capradio.org SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Content Best Practices

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

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.capradio.org 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), while the claimed language is English. Our system also found out that Community.capradio.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.

Social Sharing Optimization

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