3.8 sec in total
222 ms
3.1 sec
479 ms
Welcome to tomaze.com homepage info - get ready to check Tomaze best content right away, or after learning these important things about tomaze.com
Château La Tomaze Vignoble Lecointre propose dégustation et vente directe des vins du Val de Loire AOC : Coteaux du Layon, Cabernet d'Anjou et
Visit tomaze.comWe analyzed Tomaze.com page load time and found that the first response time was 222 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
tomaze.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value7.0 s
6/100
25%
Value6.8 s
34/100
10%
Value240 ms
86/100
30%
Value0.318
36/100
15%
Value8.8 s
35/100
10%
222 ms
374 ms
545 ms
573 ms
51 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 81% of them (44 requests) were addressed to the original Tomaze.com, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Cdn.tarteaucitron.io. The less responsive or slowest element that took the longest time to load (904 ms) belongs to the original domain Tomaze.com.
Page size can be reduced by 31.4 kB (2%)
2.1 MB
2.0 MB
In fact, the total size of Tomaze.com main page is 2.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. 35% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 21.2 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 21.2 kB or 78% of the original size.
Potential reduce by 9.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. Tomaze images are well optimized though.
Potential reduce by 765 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. Tomaze.com needs all CSS files to be minified and compressed as it can save up to 765 B or 15% of the original size.
Number of requests can be reduced by 3 (7%)
46
43
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomaze. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
tomaze.com
222 ms
tomaze.com
374 ms
www.tomaze.com
545 ms
load.js
573 ms
css2
51 ms
style.css
285 ms
main.js
647 ms
js
82 ms
lecointre.svg
104 ms
blancs-secs.png
131 ms
rouges.png
190 ms
roses.png
210 ms
blancs-moelleux.png
275 ms
bulles.png
280 ms
lecointre_tomaze-min.svg
276 ms
tomaze-vignes-loire-vin.jpg
557 ms
bio.png
304 ms
vins-tomaze.png
540 ms
cyrille-lecointre.jpg
806 ms
signature-lecointre.png
368 ms
viticulture-biologique.png
382 ms
chateau-la-tomaze.png
392 ms
vigneron-independant.png
458 ms
cepages.png
475 ms
pineau-aunis-lecointre.png
748 ms
sauvignon-symphonie-n-ix.png
547 ms
chenin-blanc-cosmo.png
567 ms
anjou-blanc-beguin.png
629 ms
pineau-aunis.png
636 ms
anjou-rouge-avant-garde.png
649 ms
anjou-villages-equinoxe.png
659 ms
six-quartiers.png
718 ms
continuum.png
725 ms
rose-de-loire-love-potion-n-ix.png
741 ms
coteaux-du-layon-atomes-crochus.png
752 ms
coteaux-du-layon-cuvee-lys.png
807 ms
coteaux-du-layon-quintessence.png
814 ms
cremant-de-loire-blanc-brut.png
835 ms
cremant-de-loire-rose-brut.png
837 ms
vins.png
844 ms
lecontre_footer.svg
894 ms
label-agriculture-biologique.png
898 ms
bio-europen.png
904 ms
S6uyw4BMUTPHvxo6WQev.woff
26 ms
S6u9w4BMUTPHh6UVewyFHi_o.woff
41 ms
S6u9w4BMUTPHh50XewyFHi_o.woff
53 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvUDTZNLo_HWo.woff
81 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vUDTZNLo_HWo.woff
67 ms
vg.png
882 ms
cvl.png
814 ms
facebook.png
812 ms
instagram.png
799 ms
tarteaucitron.min.css
408 ms
tarteaucitron.en.min.js
417 ms
tomaze.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
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.
tomaze.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
Missing source maps for large first-party JavaScript
tomaze.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
N/A
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomaze.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that Tomaze.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.
tomaze.com
Open Graph data is detected on the main page of Tomaze. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: