1.7 sec in total
105 ms
1.4 sec
257 ms
Visit splenda.la now to see the best up-to-date Splenda content for Mexico and also check out these interesting facts you probably never knew about splenda.la
¡Prueba Splenda Original, un sustituto de azúcar bajo en calorías! Conoce este edulcorante artificial Splenda o Stevia con ingredientes de origen natural
Visit splenda.laWe analyzed Splenda.la page load time and found that the first response time was 105 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
splenda.la performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value20.4 s
0/100
25%
Value3.4 s
89/100
10%
Value1,040 ms
26/100
30%
Value0.839
4/100
15%
Value26.8 s
0/100
10%
105 ms
563 ms
10 ms
41 ms
53 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 82% of them (40 requests) were addressed to the original Splenda.la, 4% (2 requests) were made to Ssl.google-analytics.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (563 ms) belongs to the original domain Splenda.la.
Page size can be reduced by 779.8 kB (45%)
1.7 MB
949.4 kB
In fact, the total size of Splenda.la main page is 1.7 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 720.3 kB which makes up the majority of the site volume.
Potential reduce by 31.7 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 31.7 kB or 74% of the original size.
Potential reduce by 8.3 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. Splenda images are well optimized though.
Potential reduce by 504.5 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 504.5 kB or 74% of the original size.
Potential reduce by 235.2 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. Splenda.la needs all CSS files to be minified and compressed as it can save up to 235.2 kB or 83% of the original size.
Number of requests can be reduced by 22 (47%)
47
25
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Splenda. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
splenda.la
105 ms
www.splenda.la
563 ms
css_GqCqCmGspWzZsDVTgkFoFb2eEt4xaByq4GFNcVi8QG4.css
10 ms
css_wH4jN1xviy3T4sU4FuPvY1IAgrSRXUcUcCIiHaxSNq8.css
41 ms
css_pJYNakruLDByz7AHSoXvEAmg3udlcd-5NBRcs9ZOfTs.css
53 ms
css_pv0fXnx8GNoFAJCnKEcswZe884xHur4ppfUBTMITOAA.css
37 ms
css_cz6ZRTkcsgfZcibmqKhzioItl21ZRpCRVlm-uNsETwc.css
51 ms
css_hX9E4hD5kYSlEgTvJPrC3k8CZKkKUemLUFvkAaB7WCw.css
40 ms
css_Cc8Ys56Z8d2PAR4PqBY1CwEHIMB4IZjCpqW0CiXKmds.css
18 ms
js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js
47 ms
js_CsS27QWlhqNas-4yV8qS_ltPxcoLoGIr7yMxUD30H28.js
38 ms
js_56rqID-GZTHtWWLqTr5fS2FWPowvNClmgeMzFigkNxo.js
50 ms
js_BQhkcrpeOhImi_xUTDZ2_7eQKZlUcs9w9_PReGgQZSU.js
93 ms
js_5_HFe9mCedCr-U5WCxMpM1aKfZ-9cxvTqTk5FD7iEjk.js
96 ms
js_wxyUlNO5AUdbKpO9Y6qvaiwUXrHWkKmW7FNYzYFnCVM.js
95 ms
js_Tes4JocZEMUxs5yMPS4nRIzRrDggJa_tx-8CdtFNhK8.js
94 ms
iframe_api
239 ms
ga.js
218 ms
all.js
208 ms
dynamic-content-boxes
123 ms
getuser
208 ms
getuser
226 ms
logo.png
41 ms
search-icon.png
40 ms
fb-login.png
40 ms
sprites-social-footer.png
41 ms
logo-home1.png
40 ms
logo-home2.png
44 ms
logo-home3.png
45 ms
logo-home4.png
45 ms
splenda-boxes-individuales1-40602-c5.jpg
78 ms
splenda-boxes-individuales2-40602-c5.jpg
77 ms
splenda-boxes-individuales4-40602-c5.jpg
52 ms
home-bg-desktop.jpg
108 ms
ajax-loader.gif
43 ms
akzidenzgrotesk-medium.woff
77 ms
akzidenzgrotesk-light.woff
62 ms
akzidenzgrotesk-light.woff
59 ms
www-widgetapi.js
146 ms
__utm.gif
24 ms
all.js
26 ms
css_xGBczeNd-RnxAwKGUMr8W_aq3Cmj51gS3HWCL8LKj2Q.css
8 ms
css_emqviflVoADFvKCCrx_RJsrA4U0SNzY9R5tOtFBo_w4.css
7 ms
css_iFygm7maxQRNl8VIGLUD3a34DZRBO6ofAQAMTlyW2Tc.css
24 ms
114 ms
xd_arbiter.php
46 ms
css_i2NSZ2dyrRZZ4Y_ai-gFUH9n4U5GiknCYJDyZR1K5i4.css
27 ms
css_lxtLXzT51m1w8gQIFvfX9x8q82DVnDs9WFBZQCSQaAo.css
15 ms
xd_arbiter.php
6 ms
splenda.la 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
splenda.la 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
splenda.la 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
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 Splenda.la 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 Splenda.la 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.
splenda.la
Open Graph description is not detected on the main page of Splenda. 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: