4 sec in total
341 ms
2.3 sec
1.4 sec
Visit whatsup.es now to see the best up-to-date Whatsup content for Mexico and also check out these interesting facts you probably never knew about whatsup.es
En las academias de inglés What's Up! aprenderás divirtiéndote sin darte cuenta. Tú eliges el horario y las clases a las que quieres ir.
Visit whatsup.esWe analyzed Whatsup.es page load time and found that the first response time was 341 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
whatsup.es performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value17.4 s
0/100
25%
Value12.6 s
3/100
10%
Value23,650 ms
0/100
30%
Value0
100/100
15%
Value36.8 s
0/100
10%
341 ms
31 ms
25 ms
84 ms
165 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 75% of them (62 requests) were addressed to the original Whatsup.es, 4% (3 requests) were made to S.ytimg.com and 2% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (761 ms) belongs to the original domain Whatsup.es.
Page size can be reduced by 1.4 MB (44%)
3.1 MB
1.7 MB
In fact, the total size of Whatsup.es main page is 3.1 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 43.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. 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.4 kB or 76% of the original size.
Potential reduce by 79.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. Whatsup images are well optimized though.
Potential reduce by 517.4 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 517.4 kB or 72% of the original size.
Potential reduce by 723.6 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. Whatsup.es needs all CSS files to be minified and compressed as it can save up to 723.6 kB or 86% of the original size.
Number of requests can be reduced by 48 (63%)
76
28
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatsup. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
whatsup.es
341 ms
css
31 ms
font-awesome.css
25 ms
system.base.css
84 ms
system.messages.css
165 ms
system.theme.css
165 ms
calendar_multiday.css
165 ms
comment.css
166 ms
date.css
171 ms
datepicker.1.7.css
171 ms
field.css
241 ms
geofield_gmap.css
242 ms
node.css
243 ms
search.css
244 ms
user.css
256 ms
views.css
255 ms
ckeditor.css
320 ms
ctools.css
327 ms
lightbox.css
323 ms
animate.css
327 ms
md-slider.css
338 ms
md-slider-style.css
341 ms
eu_cookie_compliance.css
400 ms
formblock.css
403 ms
foundation.min.css
410 ms
animate-custom.css
407 ms
custom.css
512 ms
everslider.css
422 ms
component.css
480 ms
style.css
485 ms
jquery.js
54 ms
js_IkgOrrVZK1UTp2HktvFi5vo1g7b25Muyr5GoySikuic.js
489 ms
js_g0r14t83CyFOie9dtTvScCfDLjFx09CaftsI4p5WL58.js
489 ms
js_jDzLIbkGProlF7OWqHBjdBlFoDNqTdeoSe5EXa4KLAM.js
509 ms
js_eTcoRWavHT_4Q7Ofr4OIdAE2VWYpSMTmjtFdHeY1pNg.js
561 ms
lightbox.js
567 ms
js_jdM8D9z7eK8FZ0WqqnRf6DD-XzjqdZFt9TXkG5h5OJ0.js
666 ms
js_eEqTWI9GlVf1dv7zH15f684TZ6Zqw6DZKMWBBak5tE0.js
570 ms
js_e4DJdEaFEM-bCZZKdrtMBFGavFaKm5QOUczz9ak71HM.js
677 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
582 ms
glyphicons.css
160 ms
whats-up_logo.png
114 ms
english-revolution.jpg
113 ms
slider01.jpg
363 ms
aprender-ingles-whats-up-online.jpg
363 ms
aprender-ingles-diversion-whats_up_0.jpg
363 ms
f2f3practicaras-situaciones-de-la-vida-real-negociar-comprar-viajar_2.jpg
363 ms
academia-de-ingles-rambla-de-catalunya-barcelona-whats_up.jpg
366 ms
academia-de-ingles-via-augusta-barcelona-whats_up.jpg
365 ms
academia-de-ingles-bilbao-whats_up.jpg
363 ms
academia-de-ingles-juan-bravo-madrid-whats_up_0.jpg
508 ms
academia-de-ingles-orense-madrid-whats_up.jpg
610 ms
academia-de-ingles-sabadell-whats_up.jpg
447 ms
academia-de-ingles-sevilla_whats_up-0_0.png
761 ms
academia-de-ingles-terrassa-whats-up-1.jpg
610 ms
academia-de-ingles-valencia-whats_up.jpg
609 ms
noemi-almeida.jpg
610 ms
vanessa_torrell.jpg
652 ms
gtm.js
107 ms
acwoa2-Q5Vk
331 ms
big-preloader.gif
729 ms
before-title.jpg
729 ms
after-title.jpg
729 ms
sprite2.png
729 ms
testimonios-bg.jpg
757 ms
1006294.js
255 ms
merge_light-webfont.woff
687 ms
fontawesome-webfont.woff
250 ms
merge_bold-webfont.woff
686 ms
www-embed-player-vflQrT_sR.css
254 ms
www-embed-player.js
358 ms
base.js
479 ms
analytics.js
136 ms
watch.js
733 ms
adinton.js
312 ms
collect
77 ms
collect
149 ms
adnTracker_v2.php
349 ms
ga-audiences
223 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
77 ms
ad_status.js
82 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
83 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
94 ms
whatsup.es accessibility score
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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
whatsup.es 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
Issues were logged in the Issues panel in Chrome Devtools
whatsup.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatsup.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Whatsup.es 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.
whatsup.es
Open Graph description is not detected on the main page of Whatsup. 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: