10.4 sec in total
1.7 sec
8.5 sec
215 ms
Welcome to wsa-mobile.org homepage info - get ready to check WSA Mobile best content right away, or after learning these important things about wsa-mobile.org
Visit wsa-mobile.orgWe analyzed Wsa-mobile.org page load time and found that the first response time was 1.7 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wsa-mobile.org performance score
name
value
score
weighting
Value3.7 s
28/100
10%
Value7.2 s
5/100
25%
Value4.3 s
75/100
10%
Value520 ms
56/100
30%
Value0
100/100
15%
Value10.8 s
22/100
10%
1712 ms
205 ms
212 ms
325 ms
328 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 85% of them (78 requests) were addressed to the original Wsa-mobile.org, 4% (4 requests) were made to Wsis-award.org and 3% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Wsa-mobile.org.
Page size can be reduced by 875.8 kB (26%)
3.4 MB
2.5 MB
In fact, the total size of Wsa-mobile.org main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 47.5 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 6.5 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 47.5 kB or 83% of the original size.
Potential reduce by 185.6 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. WSA Mobile images are well optimized though.
Potential reduce by 282.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 282.7 kB or 67% of the original size.
Potential reduce by 360.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. Wsa-mobile.org needs all CSS files to be minified and compressed as it can save up to 360.0 kB or 84% of the original size.
Number of requests can be reduced by 53 (60%)
89
36
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WSA Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
wsa-mobile.org
1712 ms
content-module.css
205 ms
ckeditor.css
212 ms
date.css
325 ms
datepicker.css
328 ms
timeentry.css
214 ms
filefield.css
306 ms
fivestar.css
317 ms
oxygen.css
322 ms
lightbox.css
504 ms
node.css
420 ms
defaults.css
441 ms
system.css
581 ms
system-menus.css
443 ms
user.css
512 ms
views_slideshow.css
524 ms
views_slideshow.css
546 ms
views_slideshow.css
547 ms
calendar.css
612 ms
farbtastic.css
527 ms
fieldgroup.css
539 ms
views.css
562 ms
style.css
921 ms
typography.css
596 ms
superfish.css
633 ms
superfish-navbar.css
643 ms
superfish-vertical.css
668 ms
acquia-prosper-style.css
911 ms
gray.css
906 ms
grid16-960.css
738 ms
local.css
1054 ms
jquery.js
1084 ms
drupal.js
845 ms
fivestar.js
954 ms
lightbox.js
1106 ms
jquery.cycle.all.min.js
1121 ms
views_slideshow.js
927 ms
views_slideshow.js
957 ms
views_slideshow.js
1025 ms
base.js
973 ms
ajax_view.js
968 ms
jquery.bgiframe.min.js
971 ms
hoverIntent.js
990 ms
supposition.js
1010 ms
supersubs.js
938 ms
superfish.js
964 ms
screenshot.js
947 ms
script.js
955 ms
jquery.corner.js
911 ms
acquia-prosper-script.js
930 ms
ga.js
75 ms
youtube.png
5657 ms
nlButton.jpg
5658 ms
e79sfSjdgiw
106 ms
acquia_prosper_logo.png
5607 ms
Untitled-12_0.jpg
5612 ms
feed.png
5608 ms
wsa_logo_2015_rgb.jpg
5616 ms
menu-leaf.png
5606 ms
Bild1_0.png
5618 ms
call%20web_small_0.png
5612 ms
02-HomePage.png
5613 ms
6a38d746b3_0.png
5618 ms
6VZVEuaslY1fTB8u9JibXyKQGprnn66Jz5hf4G4NaaH-qh6d0O6bfnBDpm2334cg9zU=h310.png
5616 ms
Screen%20shot%202013-10-25%20at%2010.41.07%20AM_0.png
5619 ms
0.0b_home_0.jpg
5613 ms
5I9WoStjbLrichLxIQsBCA2U81axrXr7T4x0uZNh0AyTXRDrttjk-NZ3oG-XU4m1D_g=h900_0.jpg
5613 ms
1_1.jpeg
5615 ms
Unbenannt_0.JPG
5616 ms
3fZE8e_YOgKhGN0OT6ImObpC8NvRgyCw4n90XTihZQ-OigYdKu2XdIoedllo8vbx0rQ=h310_0.png
5617 ms
nexus_10_2013-4-19-23-24-3_0.png
5618 ms
call%20web_small.png
5620 ms
WSA%20Winners%202015_web2_0.png
5622 ms
Bild2.png
5618 ms
Jury%20process%20NL.png
5618 ms
WSA%20nominees.PNG
5620 ms
CALLOPEN_0.png
5620 ms
WSA_150203_0758_2342.jpg
5619 ms
16241478913_068f7da089_z.jpg
5621 ms
Arko%20won%20in%20Manila.png
5621 ms
WSA_150201_0142_0380.jpg
5621 ms
flickr.png
5605 ms
facebook.png
5606 ms
Twitter.png
5607 ms
__utm.gif
13 ms
www-embed-player-vflfNyN_r.css
24 ms
www-embed-player.js
42 ms
base.js
5459 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
45 ms
ad_status.js
30 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
47 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
50 ms
wsa-mobile.org 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.
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
Links do not have a discernible name
wsa-mobile.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
wsa-mobile.org SEO score
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 Wsa-mobile.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 Wsa-mobile.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.
wsa-mobile.org
Open Graph description is not detected on the main page of WSA Mobile. 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: