6.4 sec in total
1.1 sec
4.9 sec
397 ms
Visit freshthyme.com now to see the best up-to-date Fresh Thyme content for United States and also check out these interesting facts you probably never knew about freshthyme.com
Shop Fresh Thyme online or find a location near you! We provide fresh, organic and natural foods from reliable sources at affordable prices. Shop today!
Visit freshthyme.comWe analyzed Freshthyme.com page load time and found that the first response time was 1.1 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
freshthyme.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value16.0 s
0/100
25%
Value5.2 s
60/100
10%
Value2,380 ms
5/100
30%
Value0.853
4/100
15%
Value18.6 s
3/100
10%
1083 ms
89 ms
98 ms
68 ms
90 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 13% of them (12 requests) were addressed to the original Freshthyme.com, 49% (46 requests) were made to Freshthyme.grocerypress.com and 5% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Freshthyme.inserts2online.com.
Page size can be reduced by 2.5 MB (43%)
5.8 MB
3.3 MB
In fact, the total size of Freshthyme.com main page is 5.8 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. 85% 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 170.7 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 36.1 kB, which is 17% 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 170.7 kB or 80% of the original size.
Potential reduce by 107.7 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. Fresh Thyme images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 70% of the original size.
Potential reduce by 846.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. Freshthyme.com needs all CSS files to be minified and compressed as it can save up to 846.4 kB or 92% of the original size.
Number of requests can be reduced by 40 (47%)
85
45
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fresh Thyme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
freshthyme.com
1083 ms
style.css
89 ms
bootstrap.min.css
98 ms
css
68 ms
style.css
90 ms
jquery.js
96 ms
jquery-migrate.min.js
88 ms
maxmind.js
87 ms
freshthyme.prod.min.js
2655 ms
scripts.js
296 ms
css
85 ms
css
92 ms
css
92 ms
app.css
292 ms
modernizr-custom.3.0.js
91 ms
style.css
690 ms
clientstyle.css
296 ms
js.js
292 ms
owl.carousel.css
291 ms
owl.carousel.js
292 ms
css
282 ms
jquery.parallax-1.1.3.js
289 ms
addthis_widget.js
40 ms
output.css
287 ms
bootstrap.min.js
285 ms
init.js
28 ms
ga.js
214 ms
jsapi_en-us.js
86 ms
svg.js
29 ms
__utm.gif
102 ms
collect
54 ms
gpt.js
6 ms
pubads_impl_81.js
10 ms
container.html
68 ms
loader.gif
64 ms
powered-by.png
64 ms
11887160_1628235987426641_1312707488_n.jpg
65 ms
12141850_786146598161490_1125510173_n.jpg
63 ms
11349354_979116262131625_1513889029_n.jpg
65 ms
11249412_1704455986439954_1682417098_n.jpg
64 ms
11850278_807643719349867_869264962_n.jpg
63 ms
12445974_776077882536061_2030536832_n.jpg
63 ms
logo.png
62 ms
powered-by.png
62 ms
homepage_cta_weekly_ads.png
64 ms
placement_1.jpg
63 ms
placement_2.jpg
62 ms
GP_0017_Tri-coloured-Quinoa-Chowder.jpg
69 ms
GP_0054_Radish-Kefir-Soup.jpg
64 ms
Strawberry-Spinach-Quesadillas.jpg
64 ms
GP_0000_Grilled-Zucchini-Salad.jpg
70 ms
Coconut-Goji-Berry-Snowball-Truffles.jpg
66 ms
Persian-Eggplant.jpg
64 ms
freshthyme-footer-logo.png
62 ms
sdk.js
200 ms
footer_grunge.png
6 ms
wood_bg_pattern.jpg
21 ms
Archer-Bold-Pro.woff
20 ms
ArcherBold.woff
19 ms
a_love_of_thunder-webfont.woff
19 ms
icomoon.ttf
69 ms
right-arrow.png
55 ms
left-arrow.png
55 ms
gingham_pattern50.png
46 ms
cta-select.png
45 ms
events-head-icon.png
46 ms
windmill-rotate.gif
66 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
64 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
65 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
65 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
65 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
66 ms
footer-select.png
60 ms
printfriendly.js
300 ms
292 ms
fruit_3a.png
73 ms
ping
66 ms
300lo.json
34 ms
fruit_1a.png
165 ms
fruit_1b.png
163 ms
fruit_2a.png
165 ms
xd_arbiter.php
170 ms
xd_arbiter.php
322 ms
store-opening_terre.jpg
53 ms
store-opening_GR2.jpg
34 ms
Cobb-Salad.jpg
35 ms
Thai-Squash-Soup.jpg
35 ms
sh.7c7179124ea24ac6ba46caac.html
67 ms
jsonAPI.jsp
104 ms
2F6A38_0_0.woff
11 ms
nr-852.min.js
77 ms
update.min.js
23 ms
f.png
36 ms
freshthyme.com 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
button, link, and menuitem elements do not have accessible names.
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
[id] attributes on active, focusable elements are not unique
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
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.
freshthyme.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
Missing source maps for large first-party JavaScript
freshthyme.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freshthyme.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 Freshthyme.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.
freshthyme.com
Open Graph description is not detected on the main page of Fresh Thyme. 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: