4.7 sec in total
149 ms
2.7 sec
1.8 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 149 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
whatsup.es performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value26.6 s
0/100
25%
Value6.1 s
44/100
10%
Value720 ms
41/100
30%
Value0.038
100/100
15%
Value8.8 s
35/100
10%
149 ms
738 ms
74 ms
145 ms
213 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 88% of them (84 requests) were addressed to the original Whatsup.es, 5% (5 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (891 ms) belongs to the original domain Whatsup.es.
Page size can be reduced by 207.5 kB (2%)
8.6 MB
8.4 MB
In fact, the total size of Whatsup.es main page is 8.6 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. 75% 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 8.2 MB which makes up the majority of the site volume.
Potential reduce by 178.6 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 178.6 kB or 85% of the original size.
Potential reduce by 15.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. Whatsup images are well optimized though.
Potential reduce by 7.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.9 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 5.9 kB or 11% of the original size.
Number of requests can be reduced by 19 (23%)
84
65
The browser has sent 84 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 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} 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
Browser errors were logged to the console
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.
{{og_description}}
whatsup.es
Open Graph data is detected on the main page of Whatsup. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: