3.2 sec in total
158 ms
2.7 sec
365 ms
Welcome to ez-ftz.com homepage info - get ready to check Ez Ftz best content right away, or after learning these important things about ez-ftz.com
Streamline your global trade management process with trade compliance information and productivity tools that automate routine tasks, give you compliance confidence, and save time | by Thomson Reuters...
Visit ez-ftz.comWe analyzed Ez-ftz.com page load time and found that the first response time was 158 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ez-ftz.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value28.9 s
0/100
25%
Value13.4 s
2/100
10%
Value6,270 ms
0/100
30%
Value0.068
96/100
15%
Value35.2 s
0/100
10%
158 ms
1010 ms
58 ms
13 ms
27 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ez-ftz.com, 45% (38 requests) were made to Tax.thomsonreuters.com and 22% (19 requests) were made to App-data.gcs.trstatic.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Store.tax.thomsonreuters.com.
Page size can be reduced by 1.1 MB (28%)
3.9 MB
2.8 MB
In fact, the total size of Ez-ftz.com main page is 3.9 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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 711.9 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 113.6 kB, which is 14% 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 711.9 kB or 89% of the original size.
Potential reduce by 121.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. Ez Ftz images are well optimized though.
Potential reduce by 277.0 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 277.0 kB or 17% of the original size.
Potential reduce by 784 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. Ez-ftz.com has all CSS files already compressed.
Number of requests can be reduced by 43 (68%)
63
20
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ez Ftz. 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 9 to 1 for CSS and as a result speed up the page load time.
ez-ftz.com
158 ms
global-trade-management
1010 ms
datadog-rum.js
58 ms
clientlib-bayberry.min.css
13 ms
clientlib-bayberry.min.js
27 ms
clientlib-dcl_components.min.css
40 ms
clientlib-dcl_components.min.js
46 ms
schemaFunctions.min.js
74 ms
highlight.js
85 ms
clientlib-base.min.css
45 ms
otSDKStub.js
73 ms
adrum-21.4.0.3405.js
53 ms
clientlib-site.min.css
45 ms
main.css
55 ms
head.js
78 ms
enterprise.js
74 ms
jquery.min.js
51 ms
utils.min.js
76 ms
granite.min.js
52 ms
clientlibs-gated-content.min.js
52 ms
esw.min.js
78 ms
clientlibs.min.css
51 ms
clientlibs.min.js
51 ms
tracking-clientlibs.min.js
69 ms
main.js
83 ms
clientlib-dependencies.min.js
77 ms
clientlib-site.min.js
68 ms
container.min.js
73 ms
clientlib-base.min.js
72 ms
pagestyle-clientlibs.min.css
79 ms
css2
43 ms
css2
17 ms
68d13ac7-d0f0-4279-827a-39220fe2e40e.json
314 ms
launch-180ff4990fd5.min.js
357 ms
gtm.js
392 ms
tr_spiral_pattern_desktop.png
317 ms
token.json
305 ms
xe1DFDPBF9qHmY9HPgviup.jpg
425 ms
support-background-full-size
413 ms
cart.json
1155 ms
0.js
181 ms
4.js
401 ms
43.js
215 ms
16.js
215 ms
tr-rebranded-logo.svg
178 ms
bb-Pattern-diagonal-v1.5.png
177 ms
233231.png
212 ms
play-icon.svg
180 ms
refresh-69-small.svg
227 ms
settings-gear-63-small.svg
228 ms
chart-bar-small.svg
229 ms
233232.png
277 ms
233233.png
1154 ms
237328.jpeg
302 ms
233235.png
397 ms
233236.png
1153 ms
brand-right-arrow.svg
303 ms
search-icon-v1.5.svg
317 ms
support-icon-v1.5.svg
395 ms
apps-icon-v1.5.svg
396 ms
user-icon-v1.5.svg
398 ms
F25puETAg8RpUxnVRrAwoo.jpg
314 ms
recaptcha__en.js
315 ms
knowledge2017-regular-webfont.woff
83 ms
knowledge2017-medium-webfont.woff
83 ms
knowledge2017-light-webfont.woff
83 ms
knowledge2017-ultralight-webfont.woff
132 ms
knowledge2017-bold-webfont.woff
131 ms
knowledge2017-black-webfont.woff
159 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky461EN.ttf
272 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KyK61EN.ttf
989 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm61EN.ttf
1009 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7FEN.ttf
1011 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7FEN.ttf
1011 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw47FEN.ttf
1010 ms
knowledge2017-regularitalic-webfont.woff
156 ms
knowledge2017-mediumitalic-webfont.woff
157 ms
knowledge2017-lightitalic-webfont.woff
170 ms
knowledge2017-ultralightitalic-webfont.woff
170 ms
knowledge2017-bolditalic-webfont.woff
248 ms
knowledge2017-blackitalic-webfont.woff
248 ms
location
986 ms
085b9c2cdb7e88297c457b.jpg
840 ms
df8771441fa7fd0a7912c2.jpg
841 ms
otBannerSdk.js
45 ms
ez-ftz.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
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ez-ftz.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
Missing source maps for large first-party JavaScript
ez-ftz.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 Ez-ftz.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 Ez-ftz.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.
ez-ftz.com
Open Graph data is detected on the main page of Ez Ftz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: