3.8 sec in total
364 ms
3.3 sec
209 ms
Visit theodor.com now to see the best up-to-date THEODOR content and also check out these interesting facts you probably never knew about theodor.com
Online order of black teas, green teas, rooibos, herbal teas, and other creations signed THEODOR. Discover our tea universes!
Visit theodor.comWe analyzed Theodor.com page load time and found that the first response time was 364 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
theodor.com performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value11.9 s
0/100
25%
Value12.3 s
3/100
10%
Value130 ms
96/100
30%
Value1.016
2/100
15%
Value10.4 s
24/100
10%
364 ms
413 ms
94 ms
184 ms
265 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Theodor.com, 87% (79 requests) were made to Theodor.fr and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (696 ms) relates to the external source Theodor.fr.
Page size can be reduced by 71.0 kB (10%)
724.0 kB
653.0 kB
In fact, the total size of Theodor.com main page is 724.0 kB. 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 464.9 kB which makes up the majority of the site volume.
Potential reduce by 38.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. 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 38.1 kB or 78% of the original size.
Potential reduce by 1.9 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. THEODOR images are well optimized though.
Potential reduce by 17.1 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 17.1 kB or 11% of the original size.
Potential reduce by 14.0 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. Theodor.com needs all CSS files to be minified and compressed as it can save up to 14.0 kB or 24% of the original size.
Number of requests can be reduced by 47 (56%)
84
37
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of THEODOR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
theodor.com
364 ms
413 ms
reset_base.css
94 ms
foundation.css
184 ms
font.css
265 ms
global.css
262 ms
highdpi.css
264 ms
responsive-tables.css
264 ms
blockcart.css
265 ms
jquery.bxslider.css
268 ms
blockcontact.css
348 ms
blocknewsletter.css
349 ms
jquery.autocomplete.css
348 ms
product_list.css
350 ms
homeslider.css
351 ms
superfish-modified.css
353 ms
anet_cookie_cnil.css
432 ms
blockpermanentlinks.css
433 ms
jquery.mCustomScrollbar.css
439 ms
theodor.css
524 ms
jquery-1.11.0.min.js
536 ms
jquery-migrate-1.2.1.min.js
442 ms
jquery.easing.js
518 ms
tools.js
520 ms
global.js
533 ms
15-jquery.total-storage.min.js
534 ms
ajax-cart.js
604 ms
jquery.scrollTo.js
604 ms
jquery.serialScroll.js
607 ms
jquery.bxslider.js
609 ms
blocknewsletter.js
611 ms
jquery.autocomplete.js
611 ms
blocksearch.js
688 ms
homeslider.js
689 ms
hoverIntent.js
692 ms
superfish-modified.js
695 ms
blocktopmenu.js
695 ms
css
33 ms
conversion.js
33 ms
GoogleAnalyticActionLib.js
696 ms
anet_cookie_cnil.js
689 ms
index.js
595 ms
jquery.selectbox-0.2.min.js
530 ms
jquery.mCustomScrollbar.concat.min.js
530 ms
onmediaquery.js
528 ms
theodor.js
533 ms
analytics.js
65 ms
tagv7.pkmin.js
424 ms
tracker.js
598 ms
transport2.png
492 ms
burger.png
200 ms
theodor-logo_mobile-1542202638.jpg
204 ms
theodor-logo-1542208172.jpg
203 ms
panier.png
202 ms
panier_dot.png
204 ms
burger-close.png
203 ms
search.png
214 ms
907aa8643b49f9c65726ae0f7dab45f38b3489f0_THEODOR-coffret-paresse-mob-en.JPG
259 ms
8f76906c9406bc444b34115487d3fa891b7f3a08_THEODOR-besoin-pause-mob-EN.JPG
304 ms
44494b13ef15036ee08e6e057cef3e79fda55107_THEODOR-thes-nat-mob-EN.JPG
215 ms
4d28100c8bf9c9b55c40014d00050f1e9627f980_THEODOR-fdp-mob-EN.JPG
304 ms
logo-theodora.png
215 ms
54872bca8c4f3a02d7a12f0a27f4174eab1a7860_pancake-matcha.JPG
307 ms
9b50714eb28e84ea3a71e6cdc7f6ae12f17c93d6_matcha-yuzu.JPG
303 ms
3759d927696dad23a5fdc58eb38f1e17f3beae37_theodora.JPG
305 ms
BellGothicBT-Roman_gdi.woff
312 ms
BellGothicStd-Bold.woff
360 ms
ec.js
24 ms
sprite-footer.png
331 ms
social-facebook.png
331 ms
social-twitter.png
332 ms
social-instagram.png
332 ms
social-google.png
360 ms
social-it.png
407 ms
social-pinterest.png
408 ms
you_tube.jpg
407 ms
linkedin.png
419 ms
BellGothicStd-Black.woff
407 ms
collect
123 ms
automation.js
124 ms
128 ms
7d28e95a9d716e868292ae07f48c91660a81f481_4d78cb827e45194cd3fca285a4a9ebc963db14fd_bandeau_coffret-paresse-en.jpg
404 ms
a1381d080bcf3ed521e860d240634cfbc06d540a_bandeau-besoin-pause-EN.JPG
369 ms
e4087b7dc04be0517c6b4175dc24c01ae1566968_bandeau-fdp-EN.jpg
453 ms
bdd6d925aed209d9a25c91040a62e9663ff574e1_bandeau-fdp-EN.jpg
372 ms
bx_loader.gif
371 ms
fleche-gauche-slider.png
377 ms
fleche-droite-slider.png
455 ms
collect
34 ms
27 ms
print.css
87 ms
theodor.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.
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
Links do not have a discernible name
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.
theodor.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
theodor.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Theodor.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Theodor.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.
theodor.com
Open Graph description is not detected on the main page of THEODOR. 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: