2.9 sec in total
17 ms
2.5 sec
371 ms
Click here to check amazing Optimizely content for Spain. Otherwise, check out these important facts you probably never knew about optimizely.es
Creating digital experiences that transform your company takes data-driven decisions, continued experimentation and constant invention.
Visit optimizely.esWe analyzed Optimizely.es page load time and found that the first response time was 17 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
optimizely.es performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value19.1 s
0/100
25%
Value13.7 s
2/100
10%
Value4,010 ms
1/100
30%
Value0.537
14/100
15%
Value22.9 s
1/100
10%
17 ms
273 ms
84 ms
32 ms
140 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Optimizely.es, 14% (11 requests) were made to D1qmdf3vop2l07.cloudfront.net and 9% (7 requests) were made to Optimizely.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source 4391536040.cdn.optimizely.com.
Page size can be reduced by 685.3 kB (68%)
1.0 MB
324.4 kB
In fact, the total size of Optimizely.es main page is 1.0 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. 50% of websites need less resources to load. Javascripts take 913.5 kB which makes up the majority of the site volume.
Potential reduce by 55.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. This page needs HTML code to be minified as it can gain 10.8 kB, which is 16% 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 55.4 kB or 81% of the original size.
Potential reduce by 31 B
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. Obviously, Optimizely needs image optimization as it can save up to 31 B or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 605.3 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 605.3 kB or 66% of the original size.
Potential reduce by 24.5 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. Optimizely.es needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 90% of the original size.
Number of requests can be reduced by 45 (64%)
70
25
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Optimizely. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
optimizely.es
17 ms
www.optimizely.es
273 ms
84 ms
jquery-modernizr.min.24d84f40.js
32 ms
4391536040.js
140 ms
css
114 ms
styles.cb86bf70.css
359 ms
_biz-a.js
572 ms
es_ES.27d17989.js
74 ms
commons.96edb61c.js
73 ms
bundle.de217f6c.js
334 ms
homepage.4193d913.js
93 ms
analytics.min.js
552 ms
widgets.js
713 ms
ip.json
626 ms
geo2.js
648 ms
event
630 ms
4391536040.html
1182 ms
event
645 ms
heap-411455962.js
704 ms
homepagegraph.svg
660 ms
email.svg
611 ms
info_box_1.svg
617 ms
info_box_2.svg
647 ms
info_box_3.svg
676 ms
nytimes.svg
679 ms
sony_gray.svg
754 ms
microsoft_gray.svg
755 ms
nbc_universal_gray.svg
758 ms
charlotterusse.svg
756 ms
linkedin_blue_circle.svg
807 ms
insight.min.js
586 ms
activityi;src=4436003;type=conve0;cat=Optim0;ord=9927908806130.29
623 ms
activityi;src=4436003;type=remar0;cat=Optim00;ord=8179217136930.674
653 ms
q8GATaKQ.min.js
652 ms
proximanova-reg.woff
525 ms
proximanova-medium.woff
560 ms
proximanova-light.woff
601 ms
p
839 ms
adsct
542 ms
conversion_async.js
486 ms
analytics.js
480 ms
lio.js
556 ms
i
807 ms
7009.js
515 ms
munchkin.js
511 ms
bBf.js
511 ms
totango3.js
514 ms
event
191 ms
event
260 ms
ip.json
219 ms
pixel
161 ms
h
175 ms
167 ms
munchkin.js
96 ms
s
122 ms
io.min.js
269 ms
undefined
65 ms
u
101 ms
pixel
48 ms
visitWebPage
645 ms
collect
28 ms
forms.min.js
92 ms
140 ms
ga-audiences
89 ms
collect
9 ms
default
42 ms
default
60 ms
1397
88 ms
ipv
173 ms
stylesheet.v2.css
36 ms
i
230 ms
default
42 ms
BizibleAcct.js
72 ms
ui-bg_flat_75_ffffff_40x100.png
11 ms
u
37 ms
17 ms
optimizely.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 have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
optimizely.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
optimizely.es 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Optimizely.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Optimizely.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.
optimizely.es
Open Graph data is detected on the main page of Optimizely. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: