7.3 sec in total
612 ms
5.8 sec
899 ms
Welcome to fonseca.pt homepage info - get ready to check Fonseca best content for United States right away, or after learning these important things about fonseca.pt
Since 1815 producing the best and most iconic Port wines. Learn about our Vintage, Tawny, Ruby and White Ports. Visit us in Gaia and the Douro Valley.
Visit fonseca.ptWe analyzed Fonseca.pt page load time and found that the first response time was 612 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fonseca.pt performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value6.3 s
10/100
25%
Value5.2 s
60/100
10%
Value580 ms
51/100
30%
Value0
100/100
15%
Value11.6 s
18/100
10%
612 ms
636 ms
31 ms
46 ms
63 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 73% of them (87 requests) were addressed to the original Fonseca.pt, 8% (10 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Fonseca.pt.
Page size can be reduced by 577.9 kB (10%)
6.0 MB
5.4 MB
In fact, the total size of Fonseca.pt main page is 6.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. 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 5.4 MB which makes up the majority of the site volume.
Potential reduce by 256.1 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 152.0 kB, which is 56% 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 256.1 kB or 94% of the original size.
Potential reduce by 319.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. Fonseca images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 183 B
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. Fonseca.pt has all CSS files already compressed.
Number of requests can be reduced by 38 (37%)
103
65
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fonseca. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fonseca.pt
612 ms
en
636 ms
bootstrap.min.css
31 ms
css2
46 ms
css2
63 ms
css2
68 ms
style_frontend.9fb9e678.css
187 ms
style_frontend_mobile.0d3e3485.css
184 ms
star-rating.css
175 ms
animate.min.css
181 ms
tiny-slider.css
51 ms
owl.carousel.min.css
37 ms
owl.theme.default.min.css
41 ms
api.js
53 ms
recaptcha__en.js
25 ms
jquery-3.6.0.min.js
208 ms
jqueryconfirm.js
205 ms
jquery-ui.min.js
14 ms
owl.carousel.min.js
207 ms
star-rating.js
205 ms
wow.min.js
205 ms
bootstrap.bundle.min.js
5 ms
tiny-slider.js
13 ms
frontend.d8f31541.js
207 ms
816238134
165 ms
816238134
218 ms
812433500
306 ms
fb.svg
290 ms
insta.svg
291 ms
youtube.svg
293 ms
twitter.svg
294 ms
nav-down.svg
297 ms
nav-up-hover.svg
298 ms
nav_logo.svg
299 ms
branding-white-font.svg
302 ms
angle-right.svg
301 ms
angle-right.png
303 ms
icon-search.svg
303 ms
nav_logo_mobile.svg
304 ms
hamb-mobile.svg
316 ms
close.png
317 ms
file_63f8d5f90c1296.25608710
1002 ms
file_63f8e6dfc363c4.66259854
1151 ms
file_63f8e77571d227.67710791
1018 ms
file_64ef0b090c7428.93812037
718 ms
pipas-bg.png
831 ms
logo-homepage.svg
416 ms
file_63f375f8a78685.54484674
1336 ms
file_63f75671b06fe2.53163989
1372 ms
file_63f7577faf5922.39562540
1220 ms
file_63f757fdc35c94.31735289
1423 ms
section_4_bg.png
1287 ms
icons-caves.svg
1236 ms
icons-vinha.svg
1307 ms
image_641348e79cba75.69307388
1806 ms
image_641b2fb1843572.85885274
1956 ms
image_642d3049648d33.81250374
1911 ms
image_642d36942841a6.12944905
2026 ms
image_64089a0b5c1383.41115478
1942 ms
image_642d39bca0d6e4.09767037
1773 ms
image_642d374071d307.82499301
2207 ms
image_642d345e570e08.26762521
2206 ms
816238134
161 ms
816238134
214 ms
gtm.js
102 ms
H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFhFTQ7Q.ttf
55 ms
H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFiNTQ7Q.ttf
80 ms
H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFk9TQ7Q.ttf
89 ms
H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFs9UQ7Q.ttf
137 ms
H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFvZUQ7Q.ttf
138 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf
138 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf
136 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf
90 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf
138 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf
139 ms
image_642d3470b93649.08045892
2200 ms
image_66867240e9ec77.39686825
2081 ms
file_63f75482a37f74.50621503
2339 ms
file_63f75f0c658da5.21120984
2339 ms
bin.png
2111 ms
close.png
2144 ms
home_image
2506 ms
home_image
2571 ms
home_image
2685 ms
home_image
2641 ms
subfooter_left_image_6422fb5dca1fc7.08866630
2874 ms
subfooter_right_image_6422fb5dcbd295.11815581
2800 ms
file_63f75db0e50f29.38143253
2907 ms
angle-right.png
2641 ms
banner_6626ee465806d0.12643735
3332 ms
api.js
59 ms
js
72 ms
fbevents.js
36 ms
banner_649aad010b7399.57442034
2928 ms
935857114996891
76 ms
206657785393925
41 ms
banner_64241267b9ee82.29279619
2794 ms
banner_6411e37899cc47.03862574
2741 ms
banner_6411e42b06bbd2.04978473
2618 ms
banner_6411e49bb773c5.54949421
2653 ms
banner_6411e4e96fa465.84574116
2640 ms
banner_6411e5590a3168.05386634
2718 ms
banner_6411e75542f010.54296092
2780 ms
banner_6411e7c94dfbe8.31127599
2867 ms
banner_6411e81cdebe92.96166691
2946 ms
banner_6412f64fe6dcd8.22788304
2910 ms
banner_6412f7457e3248.07761470
2967 ms
banner_6412f7f48c9ae9.55824374
3040 ms
branding-favicon.svg
2298 ms
angle-right.png
2310 ms
i010898.png
2328 ms
angle-down.png
2323 ms
fb_bl.svg
2278 ms
insta_bl.svg
2199 ms
youtube_bl.svg
2025 ms
twitter_bl.svg
2014 ms
arrow-left-mobile.svg
2046 ms
close-white.png
2016 ms
owl-left.svg
1988 ms
owl-right.svg
1953 ms
fonseca.pt 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
<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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
fonseca.pt 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
fonseca.pt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fonseca.pt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Fonseca.pt 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.
fonseca.pt
Open Graph data is detected on the main page of Fonseca. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: