Tools & Wizards About Us
gospelhoje.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

gospelhoje.com

Radio Gospel Evangelica

Page Load Speed

2.4 sec in total

First Response

53 ms

Resources Loaded

2.2 sec

Page Rendered

184 ms

gospelhoje.com screenshot

About Website

Welcome to gospelhoje.com homepage info - get ready to check Gospel Hoje best content for Brazil right away, or after learning these important things about gospelhoje.com

Radio FM Evangélica Gospel Cordeiro de Deus online, muito boa para quem busca a presença de Deus. O som que vem do céu para o seu coração transmitindo do Brasil para todos os países do mundo no ar des...

Visit gospelhoje.com

Key Findings

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

Performance Metrics

gospelhoje.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

gospelhoje.com

53 ms

gospelhoje.com

59 ms

www.gospelhoje.com

24 ms

radioc.com.br

711 ms

bootstrap.min.css

34 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Gospelhoje.com, 44% (30 requests) were made to Public-rf-assets.minhawebradio.net and 10% (7 requests) were made to Cbox.im. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Radioc.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.7 kB (7%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gospelhoje.com main page is 1.4 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. 65% of websites need less resources to load. Images take 728.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 66.9 kB

  • Original 88.3 kB
  • After minification 78.3 kB
  • After compression 21.4 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. This page needs HTML code to be minified as it can gain 10.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.9 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 26.6 kB

  • Original 728.8 kB
  • After minification 702.1 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. Gospel Hoje images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.9 kB

  • Original 498.0 kB
  • After minification 498.0 kB
  • After compression 496.1 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

-5%

Potential reduce by 3.2 kB

  • Original 68.7 kB
  • After minification 68.7 kB
  • After compression 65.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. Gospelhoje.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (53%)

Requests Now

58

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gospelhoje.com

gospelhoje.com

53 ms

gospelhoje.com

gospelhoje.com

59 ms

www.gospelhoje.com

www.gospelhoje.com

24 ms

radioc.com.br

radioc.com.br

711 ms

bootstrap.min.css

bootstrap.min.css

34 ms

font-awesome.min.css

font-awesome.min.css

51 ms

nprogress.min.css

nprogress.min.css

43 ms

openlayers.css

openlayers.css

50 ms

main.css

main.css

42 ms

theme-main.css

theme-main.css

43 ms

theme-main-responsive.css

theme-main-responsive.css

55 ms

royalslider.css

royalslider.css

56 ms

rs-default.css

rs-default.css

55 ms

splide-core.min.css

splide-core.min.css

57 ms

player-fixed.css

player-fixed.css

58 ms

player.css

player.css

57 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

57 ms

api.js

api.js

62 ms

nprogress.min.js

nprogress.min.js

56 ms

openlayers.js

openlayers.js

60 ms

utils.js

utils.js

60 ms

main.js

main.js

60 ms

jquery.royalslider.min.js

jquery.royalslider.min.js

60 ms

splide.min.js

splide.min.js

60 ms

rf-player.js

rf-player.js

61 ms

player.js

player.js

60 ms

css2

css2

37 ms

css2

css2

26 ms

css2

css2

25 ms

recaptcha__pt_br.js

recaptcha__pt_br.js

48 ms

mobile.svg

mobile.svg

1 ms

cast_sender.js

cast_sender.js

45 ms

d677bcdf8badf60c57c803c30166149c.png

d677bcdf8badf60c57c803c30166149c.png

54 ms

radioccombr

radioccombr

351 ms

hqdefault.jpg

hqdefault.jpg

145 ms

hqdefault.jpg

hqdefault.jpg

148 ms

hqdefault.jpg

hqdefault.jpg

163 ms

hqdefault.jpg

hqdefault.jpg

154 ms

hqdefault.jpg

hqdefault.jpg

164 ms

558d1463a9a39d16c5c2931515b76d01.png

558d1463a9a39d16c5c2931515b76d01.png

7 ms

badge-pwa.png

badge-pwa.png

4 ms

generic-simple-player.css

generic-simple-player.css

10 ms

index.js

index.js

12 ms

generic-simple-player.js

generic-simple-player.js

10 ms

0016968e970d1d8dbc916efb7a2f3c95.png

0016968e970d1d8dbc916efb7a2f3c95.png

103 ms

no-broadcaster-registered.png

no-broadcaster-registered.png

12 ms

font

font

194 ms

fa-solid-900.ttf

fa-solid-900.ttf

20 ms

fa-regular-400.ttf

fa-regular-400.ttf

17 ms

fa-brands-400.ttf

fa-brands-400.ttf

19 ms

font

font

210 ms

font

font

219 ms

399 ms

100 ms

jsc_10_1662968291.js

jsc_10_1662968291.js

36 ms

IM7My.c100.jpg

IM7My.c100.jpg

502 ms

selo.png

selo.png

186 ms

sU5bP.c100.jpg

sU5bP.c100.jpg

514 ms

8jgxq.c100.jpg

8jgxq.c100.jpg

519 ms

RKje8.c100.jpg

RKje8.c100.jpg

521 ms

UTrxD.c100.jpg

UTrxD.c100.jpg

520 ms

UoXDS.c100.png

UoXDS.c100.png

521 ms

br.png

br.png

51 ms

ca.png

ca.png

65 ms

fXc7J.s32.png

fXc7J.s32.png

563 ms

css

css

16 ms

font

font

20 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

32 ms

Accessibility Review

gospelhoje.com accessibility score

52

Accessibility Issues

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

Best Practices

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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gospelhoje.com SEO score

92

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gospelhoje.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Gospelhoje.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

gospelhoje.com

Open Graph data is detected on the main page of Gospel Hoje. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: