3.1 sec in total
163 ms
2.4 sec
541 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 163 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
ez-ftz.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value25.4 s
0/100
25%
Value13.2 s
2/100
10%
Value7,830 ms
0/100
30%
Value0.078
95/100
15%
Value31.4 s
0/100
10%
163 ms
126 ms
40 ms
9 ms
33 ms
Our browser made a total of 127 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, 28% (36 requests) were made to Tax.thomsonreuters.com and 15% (19 requests) were made to App-data.gcs.trstatic.net. The less responsive or slowest element that took the longest time to load (860 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 794.8 kB (23%)
3.4 MB
2.6 MB
In fact, the total size of Ez-ftz.com main page is 3.4 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 277.6 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 64.2 kB, which is 20% 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 277.6 kB or 87% of the original size.
Potential reduce by 140.2 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 376.4 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 376.4 kB or 24% of the original size.
Potential reduce by 645 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 76 (74%)
103
27
The browser has sent 103 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 45 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ez-ftz.com
163 ms
global-trade-management
126 ms
datadog-rum.js
40 ms
clientlib-bayberry.min.css
9 ms
clientlib-bayberry.min.js
33 ms
clientlib-dcl_components.min.css
24 ms
clientlib-dcl_components.min.js
34 ms
schemaFunctions.min.js
58 ms
highlight.js
61 ms
clientlib-base.min.css
31 ms
otSDKStub.js
70 ms
adrum-21.4.0.3405.js
61 ms
clientlib-site.min.css
35 ms
main.css
75 ms
head.js
78 ms
jquery.min.js
31 ms
utils.min.js
65 ms
granite.min.js
59 ms
tracking-clientlibs.min.js
55 ms
main.js
78 ms
clientlib-dependencies.min.js
62 ms
clientlib-site.min.js
58 ms
container.min.js
64 ms
clientlib-base.min.js
61 ms
pagestyle-clientlibs.min.css
66 ms
css2
36 ms
css2
13 ms
68d13ac7-d0f0-4279-827a-39220fe2e40e.json
225 ms
launch-180ff4990fd5.min.js
330 ms
gtm.js
453 ms
tr_spiral_pattern_desktop.png
292 ms
token.json
237 ms
cart.json
830 ms
4.js
440 ms
41.js
166 ms
14.js
228 ms
28.js
227 ms
tr-logo.svg
171 ms
bb-Pattern-diagonal-v1.5.png
172 ms
233231.png
224 ms
play-icon.svg
171 ms
refresh-69-small.svg
288 ms
settings-gear-63-small.svg
286 ms
chart-bar-small.svg
284 ms
233232.png
343 ms
233233.png
435 ms
237328.jpeg
315 ms
233235.png
656 ms
233236.png
399 ms
support-background-full-size.png
387 ms
brand-right-arrow.svg
400 ms
location
320 ms
support-icon-v1.5.svg
367 ms
search-icon-v1.5.svg
369 ms
apps-icon-v1.5.svg
507 ms
user-icon-v1.5.svg
532 ms
knowledge2017-regular-webfont.woff
77 ms
knowledge2017-medium-webfont.woff
167 ms
knowledge2017-light-webfont.woff
167 ms
knowledge2017-ultralight-webfont.woff
273 ms
knowledge2017-bold-webfont.woff
194 ms
knowledge2017-black-webfont.woff
194 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky461EN_io6n6_C.ttf
473 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KyK61EN_io6n6_C.ttf
661 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm61EN_io6n6_C.ttf
662 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7FEN_io6n6_C.ttf
716 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7FEN_io6n6_C.ttf
838 ms
nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw47FEN_io6n6_C.ttf
860 ms
knowledge2017-regularitalic-webfont.woff
249 ms
knowledge2017-mediumitalic-webfont.woff
249 ms
knowledge2017-lightitalic-webfont.woff
285 ms
knowledge2017-ultralightitalic-webfont.woff
284 ms
knowledge2017-bolditalic-webfont.woff
424 ms
knowledge2017-blackitalic-webfont.woff
424 ms
EX3dceb8f81f0f4f11950a2bad96afc88a-libraryCode_source.min.js
147 ms
AppMeasurement_Module_AudienceManagement.min.js
241 ms
hotjar-13668.js
510 ms
6si.min.js
412 ms
insight.min.js
408 ms
js
184 ms
RCf5b9192f77c84ea6baec2a2775c8832f-source.min.js
177 ms
RC827dbe9d1a2d4c3a9919a18449e227aa-source.min.js
176 ms
RCd21e60c7058541e2b4cf50152255ef5f-source.min.js
315 ms
analytics.js
327 ms
otBannerSdk.js
216 ms
df8771441fa7fd0a7912c2.jpg
409 ms
085b9c2cdb7e88297c457b.jpg
408 ms
323 ms
467 ms
bat.js
266 ms
up_loader.1.1.0.js
278 ms
en.json
40 ms
rd
143 ms
img.gif
355 ms
img.gif
372 ms
otFlat.json
147 ms
otPcCenter.json
176 ms
otCommonStyles.css
176 ms
collect
131 ms
collect
310 ms
modules.f7c079ad889f2e18ab73.js
321 ms
dest5.html
256 ms
id
284 ms
json
285 ms
fbevents.js
199 ms
elqCfg.min.js
235 ms
230 ms
ot_close.svg
128 ms
TR.png
54 ms
133 ms
ga-audiences
130 ms
ibs:dpid=411&dpuuid=Zbm1NgAAAFwFqwMv
43 ms
215515565692587
756 ms
svrGP
190 ms
svrGP
159 ms
svrGP
168 ms
svrGP
166 ms
pixel
40 ms
tap.php
29 ms
rum
24 ms
svrGP
80 ms
svrgp.aspx
59 ms
bounce
12 ms
sd
29 ms
Pug
16 ms
img.gif
45 ms
partner
3 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 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
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: