6.1 sec in total
361 ms
4.1 sec
1.6 sec
Click here to check amazing Frank About Tea content. Otherwise, check out these important facts you probably never knew about frankabouttea.com
FRANK about tea is shorting the supply chain: Fresher tea for you, higher margins for local producers!
Visit frankabouttea.comWe analyzed Frankabouttea.com page load time and found that the first response time was 361 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
frankabouttea.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value7.1 s
6/100
25%
Value6.2 s
43/100
10%
Value950 ms
29/100
30%
Value0
100/100
15%
Value11.2 s
20/100
10%
361 ms
487 ms
156 ms
281 ms
155 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 74% of them (58 requests) were addressed to the original Frankabouttea.com, 5% (4 requests) were made to Use.fontawesome.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Frankabouttea.com.
Page size can be reduced by 569.4 kB (42%)
1.3 MB
771.6 kB
In fact, the total size of Frankabouttea.com main page is 1.3 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. 65% of websites need less resources to load. Images take 633.2 kB which makes up the majority of the site volume.
Potential reduce by 37.4 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 37.4 kB or 77% of the original size.
Potential reduce by 29.1 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. Frank About Tea images are well optimized though.
Potential reduce by 154.6 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 154.6 kB or 62% of the original size.
Potential reduce by 348.3 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. Frankabouttea.com needs all CSS files to be minified and compressed as it can save up to 348.3 kB or 85% of the original size.
Number of requests can be reduced by 45 (66%)
68
23
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frank About Tea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
frankabouttea.com
361 ms
487 ms
13a00bc874.js
156 ms
jquery-2.2.4.js
281 ms
grp-widget.css
155 ms
widget.css
326 ms
style.min.css
434 ms
vendors-style.css
439 ms
style.css
499 ms
woocommerce-layout.css
433 ms
woocommerce.css
437 ms
wc-quantity-increment.css
445 ms
slick.min.css
259 ms
style.css
471 ms
woocommerce.css
495 ms
cookieconsent.min.css
550 ms
grp-time.js
557 ms
jquery.js
638 ms
login-with-ajax.js
587 ms
frontend.min.js
587 ms
wc-quantity-increment.min.js
585 ms
typeform-elements.js
848 ms
js
313 ms
mc-validate.js
308 ms
jquery.blockUI.min.js
558 ms
add-to-cart.min.js
659 ms
js.cookie.min.js
659 ms
woocommerce.min.js
659 ms
cart-fragments.min.js
658 ms
tracker.min.js
766 ms
slick.min.js
280 ms
main.min.js
766 ms
cookieconsent.min.js
818 ms
postscribe.min.js
966 ms
complianz.min.js
965 ms
wp-embed.min.js
966 ms
13a00bc874.css
108 ms
font-awesome-css.min.css
8 ms
analytics.js
39 ms
collect
38 ms
collect
172 ms
ga-audiences
35 ms
gtm.js
33 ms
insight.min.js
458 ms
frankabouttea.svg
373 ms
check.svg
352 ms
cart.png
370 ms
Untitled-design-32.png
1156 ms
icon2.svg
351 ms
icon1-1.svg
356 ms
icon3.svg
477 ms
colorful_mockup_JG-1.jpg
1212 ms
check-black.svg
477 ms
Frank-about-tea-zakelijk-oplossing.png
1400 ms
Frank-about-tea-unilever-500x194.jpg
491 ms
Frank-about-tea-farm-field-schools-500x194.jpg
626 ms
Frank-about-tea-frank-about-bags-500x194.jpg
544 ms
Forbes-1.jpg
545 ms
fd-logo-01-e1569309332633.jpg
611 ms
BNR-1.jpg
611 ms
Sprout-1.jpg
1130 ms
logo5.jpg
1131 ms
logo6-1.jpg
1187 ms
collect
77 ms
manrope-regular.woff
697 ms
manrope-medium.woff
692 ms
manrope-light.woff
689 ms
manrope-thin.woff
856 ms
manrope-semibold.woff
861 ms
manrope-bold.woff
865 ms
manrope-extrabold.woff
868 ms
fontawesome-webfont.woff
49 ms
insight.old.min.js
35 ms
collect
102 ms
ga-audiences
555 ms
frankabouttea.com
889 ms
woocommerce-smallscreen.css
93 ms
22 ms
frankabouttea.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
[id] attributes on active, focusable elements are not unique
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
ARIA IDs are not unique
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.
frankabouttea.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
frankabouttea.com SEO score
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
NL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frankabouttea.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Frankabouttea.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.
frankabouttea.com
Open Graph data is detected on the main page of Frank About Tea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: