7.3 sec in total
1.7 sec
4.7 sec
798 ms
Click here to check amazing Optawines content for Portugal. Otherwise, check out these important facts you probably never knew about optawines.com
Visit optawines.comWe analyzed Optawines.com page load time and found that the first response time was 1.7 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
optawines.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.8 s
3/100
25%
Value11.5 s
5/100
10%
Value260 ms
83/100
30%
Value0.086
93/100
15%
Value7.7 s
46/100
10%
1721 ms
221 ms
64 ms
76 ms
88 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 74% of them (42 requests) were addressed to the original Optawines.com, 9% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Optawines.com.
Page size can be reduced by 652.8 kB (13%)
5.1 MB
4.4 MB
In fact, the total size of Optawines.com main page is 5.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. 50% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 29.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. This page needs HTML code to be minified as it can gain 4.6 kB, which is 12% 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 29.6 kB or 76% of the original size.
Potential reduce by 67.4 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. Optawines images are well optimized though.
Potential reduce by 325.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 325.4 kB or 74% of the original size.
Potential reduce by 230.4 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. Optawines.com needs all CSS files to be minified and compressed as it can save up to 230.4 kB or 83% of the original size.
Number of requests can be reduced by 34 (67%)
51
17
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Optawines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
optawines.com
1721 ms
language-selector.css
221 ms
css
64 ms
css
76 ms
css
88 ms
flick.css
329 ms
optawines.com
1096 ms
styles.css
239 ms
tribe-events-full.min.css
336 ms
tribe-events-theme.min.css
287 ms
navigation.css
326 ms
cms-navigation-base.css
334 ms
cms-navigation.css
401 ms
styles.f6413c85.min.css
874 ms
style.css
544 ms
jquery.js
769 ms
jquery-migrate.min.js
444 ms
scrollTo.js
511 ms
jquery.form.min.js
553 ms
mailchimp.js
621 ms
core.min.js
652 ms
datepicker.js
887 ms
bootstrap.js
947 ms
scripts.js
885 ms
modernizr.js
983 ms
scripts.js
886 ms
sitepress.js
886 ms
wp-emoji-release.min.js
765 ms
logo.png
125 ms
logo-w.png
125 ms
ico-lupa-2.png
124 ms
pt-pt.png
125 ms
en.png
124 ms
hero1.png
555 ms
hero2.png
1106 ms
opta-1.jpg
259 ms
opta-dao-branco.png
996 ms
opta-dao-rose.png
885 ms
Opta-dao-tinto.png
1755 ms
natal-01-780x450.jpg
447 ms
Wine-Merchant-top1002-780x300.jpg
559 ms
logo-ando.png
666 ms
divider.png
646 ms
sdk.js
165 ms
cd-top-arrow.svg
411 ms
oIwdBjO99oH_APMcy7EuWPesZW2xOQ-xsNqO47m55DA.ttf
44 ms
EcjpF2hW5gSZ4M16YLdG850EAVxt0G0biEntp43Qt6E.ttf
44 ms
l1JcQwKaHzEH7sWBQ9t-7p0EAVxt0G0biEntp43Qt6E.ttf
56 ms
kH7K4InNTm7mmOXXjrA5v_gg4qM5Rpmu0ASAribBgqE.ttf
73 ms
pR0sBQVcY0JZc_ciXjFsKwAUTJOA6-irsSazDq377BE.ttf
72 ms
analytics.js
27 ms
collect
31 ms
64 ms
xd_arbiter.php
147 ms
xd_arbiter.php
256 ms
tribe-events-full-mobile.min.css
115 ms
tribe-events-theme-mobile.min.css
111 ms
optawines.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
optawines.com 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
optawines.com 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Optawines.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Optawines.com 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.
optawines.com
Open Graph description is not detected on the main page of Optawines. 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: