2.1 sec in total
190 ms
1.8 sec
160 ms
Welcome to voa.com homepage info - get ready to check VOA best content for Indonesia right away, or after learning these important things about voa.com
Accurate, objective news coverage from the U.S. and around the world.
Visit voa.comWe analyzed Voa.com page load time and found that the first response time was 190 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
voa.com performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value9.1 s
1/100
25%
Value6.7 s
35/100
10%
Value1,540 ms
13/100
30%
Value0.003
100/100
15%
Value11.6 s
18/100
10%
190 ms
752 ms
40 ms
127 ms
113 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 95% of them (57 requests) were addressed to the original Voa.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to . The less responsive or slowest element that took the longest time to load (752 ms) belongs to the original domain Voa.com.
Page size can be reduced by 25.5 kB (0%)
6.2 MB
6.2 MB
In fact, the total size of Voa.com main page is 6.2 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 6.2 MB which makes up the majority of the site volume.
Potential reduce by 19.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 19.0 kB or 78% of the original size.
Potential reduce by 6.5 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. VOA images are well optimized though.
Potential reduce by 34 B
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.
Number of requests can be reduced by 20 (44%)
45
25
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VOA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
voa.com
190 ms
www.voa.com
752 ms
widgetkit-b430849a.css
40 ms
website.css
127 ms
jquery.min.js
113 ms
jquery-noconflict.js
80 ms
jquery-migrate.min.js
79 ms
caption.js
78 ms
widgetkit-68b9d06d.js
79 ms
bootstrap.min.js
113 ms
website.js
113 ms
lightbox.js
86 ms
mediaelement-and-player.js
96 ms
ga.js
81 ms
,
35 ms
slideshow.js
52 ms
logo.png
113 ms
glyphicons-halflings.png
74 ms
01-Exterior3TwilightView.jpg
341 ms
01-ABP130301_0001s.jpg
230 ms
NRF01-a.jpg
369 ms
06265.jpg
190 ms
AFHW-lobbyWIDE-0315.jpg
314 ms
001-MG_0324-a.jpg
335 ms
img-00a.jpg
229 ms
00-UNMH-Cancer-43.jpg
377 ms
01---PGC_Aquamarine_Moradia_Exterior_D_Dia.jpg
342 ms
RD1.jpg
426 ms
nav.png
372 ms
logo-dark.png
378 ms
twitter-icon.png
380 ms
facebook-icon.png
405 ms
google-icon.png
410 ms
linkedin-icon.png
413 ms
pinterest-icon.png
415 ms
vimeo-icon.png
417 ms
LanguageCulturalCenter-298x188.jpg
442 ms
TOpShopNYC-298x188.jpg
447 ms
451Tenth_StreetCrop-298x188.png
451 ms
logos-footer-dark.png
453 ms
facebook.png
455 ms
twitter.png
462 ms
linkedin.png
478 ms
pintrest.png
484 ms
googleplus.png
487 ms
vimeo.png
490 ms
OpenSans-Light.woff
499 ms
OpenSans.woff
512 ms
OpenSans-Semibold.woff
525 ms
OpenSans-Bold.woff
512 ms
Montserrat-Regular.woff
513 ms
__utm.gif
35 ms
Montserrat-Bold.woff
478 ms
fontawesome-webfont.woff
474 ms
Titillium-regular.woff
443 ms
Titillium-light.woff
378 ms
Titillium-thin.woff
344 ms
Titillium-semi-bold.woff
361 ms
Titillium-bold.woff
276 ms
blank.gif
256 ms
voa.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
voa.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
voa.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voa.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 Voa.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.
voa.com
Open Graph description is not detected on the main page of VOA. 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: