4.3 sec in total
230 ms
3.7 sec
423 ms
Visit voar.org now to see the best up-to-date VOAR content and also check out these interesting facts you probably never knew about voar.org
Lighthouse VOAR-FM Radio 96.7
Visit voar.orgWe analyzed Voar.org page load time and found that the first response time was 230 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
voar.org performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value6.6 s
8/100
25%
Value16.4 s
0/100
10%
Value2,590 ms
4/100
30%
Value0.191
64/100
15%
Value23.9 s
1/100
10%
230 ms
132 ms
740 ms
1516 ms
1607 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 55% of them (63 requests) were addressed to the original Voar.org, 15% (17 requests) were made to Html5radio.svnlabs.com and 10% (12 requests) were made to Secure.pinnion.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Voar.org.
Page size can be reduced by 898.8 kB (44%)
2.0 MB
1.1 MB
In fact, the total size of Voar.org main page is 2.0 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. 55% of websites need less resources to load. Javascripts take 927.2 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.3 kB or 76% of the original size.
Potential reduce by 38.4 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. VOAR images are well optimized though.
Potential reduce by 629.0 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 629.0 kB or 68% of the original size.
Potential reduce by 206.0 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. Voar.org needs all CSS files to be minified and compressed as it can save up to 206.0 kB or 85% of the original size.
Number of requests can be reduced by 80 (80%)
100
20
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VOAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
voar.org
230 ms
style.css
132 ms
changer.css
740 ms
colorpicker.css
1516 ms
spinner.css
1607 ms
css
25 ms
css
38 ms
styles.css
148 ms
events_manager.css
152 ms
wpv-voting.css
197 ms
fonts.php
231 ms
jquery.prettyPhoto.min.css
233 ms
jquery.jPlayer.css
262 ms
jquery.isotope.css
310 ms
mrp.js
235 ms
modernizr.custom.all.min.js
325 ms
css3MediaQueries.min.js
343 ms
jquery.js
488 ms
jquery-migrate.min.js
402 ms
jquery.easing.min.js
411 ms
core.min.js
480 ms
widget.min.js
482 ms
position.min.js
610 ms
mouse.min.js
620 ms
sortable.min.js
609 ms
datepicker.min.js
705 ms
menu.min.js
686 ms
autocomplete.min.js
689 ms
resizable.min.js
764 ms
draggable.min.js
760 ms
button.min.js
781 ms
dialog.min.js
836 ms
events-manager.js
842 ms
jscolor.js
1260 ms
wpv-userregister.js
842 ms
wpv-voterajax.js
903 ms
gd-praybox-sc.css
923 ms
jquery.prettyPhoto.min.js
913 ms
jquery.script.js
971 ms
jquery.jPlayer.min.js
972 ms
jquery.jPlayer.playlist.min.js
872 ms
jquery.tweet.min.js
902 ms
comment-reply.min.js
888 ms
jquery.form.min.js
893 ms
scripts.js
867 ms
wp-embed.min.js
888 ms
jquery.validationEngine.min.js
905 ms
jquery.validationEngine-lang.php
851 ms
wp-emoji-release.min.js
112 ms
purple.jpg
232 ms
analytics.js
21 ms
bg_i_1.jpg
257 ms
c011faf456c96173a1284c17d1d05d0a.png
214 ms
arrow_top.png
124 ms
facebook.png
122 ms
twitter.png
120 ms
flickr.png
122 ms
nav_a_hover_bg.png
203 ms
dropdown_ul_before_bg.png
196 ms
dropdown_span_bg.png
204 ms
cont_bg.png
204 ms
html5shoutcast.php
186 ms
webWidget.php
869 ms
loader_for_white.gif
190 ms
divider.png
199 ms
top_sidebar_h3_divider.png
198 ms
he-is-risen.jpg
767 ms
hand-226358_1280(2).jpg
270 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
37 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
38 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
38 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
39 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
38 ms
collect
7 ms
collect
149 ms
loader.gif
157 ms
gtm.js
65 ms
printfriendly.js
136 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
72 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
69 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
71 ms
player.css
19 ms
style.css
52 ms
slider.css
29 ms
jquery.jplayer.min.js
32 ms
random-v1.js
29 ms
jquery-1.7.2.min.js
16 ms
jquery-ui-1.8.21.custom.min.js
17 ms
ga.js
13 ms
audio.png
24 ms
twitter.png
23 ms
facebook.png
29 ms
spacer.gif
23 ms
pause-btn.png
24 ms
play-btn.png
47 ms
bg-track.png
24 ms
volume.png
30 ms
animated_favicon1.gif
29 ms
__utm.gif
11 ms
jquery.min.js
20 ms
jquery-ui.min.js
41 ms
jquery.alphanumeric.pack.(362948).js
246 ms
jquery.autoresize.(362948).js
249 ms
utf8_encode.(362948).js
249 ms
md5.(362948).js
250 ms
web_survey.(362948).css
254 ms
jquery.cookie.(362948).js
320 ms
jquery.ba-resize.min.(362948).js
487 ms
webWidgetData.php
490 ms
webWidget.(362948).js
570 ms
ga.js
21 ms
__utm.gif
11 ms
__utm.gif
28 ms
0_0_0_1_LOGO1.png
91 ms
symbols.woff
392 ms
voar.org accessibility score
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
Image elements do not have [alt] attributes
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.
voar.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
voar.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voar.org 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 Voar.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.
voar.org
Open Graph description is not detected on the main page of VOAR. 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: