Tools & Wizards About Us
eezeetags.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

eezeetags.com

Home - Eezeetags

Page Load Speed

2.6 sec in total

First Response

304 ms

Resources Loaded

1.8 sec

Page Rendered

495 ms

eezeetags.com screenshot

About Website

Visit eezeetags.com now to see the best up-to-date Eezeetags content and also check out these interesting facts you probably never knew about eezeetags.com

eezeetags® provides airports with unique linerless self-adhesive bag tags, designed around the passenger self-tagging a bag.

Visit eezeetags.com

Key Findings

We analyzed Eezeetags.com page load time and found that the first response time was 304 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

eezeetags.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value8,950 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value28.3 s

0/100

10%

Network Requests Diagram

eezeetags.com

304 ms

eezeetags.com

428 ms

style.css

191 ms

css

295 ms

manifest.js

281 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 83% of them (29 requests) were addressed to the original Eezeetags.com, 11% (4 requests) were made to Ssl.p.jwpcdn.com and 3% (1 request) were made to Privacy-policy.u-lab.nl. The less responsive or slowest element that took the longest time to load (701 ms) relates to the external source Privacy-policy.u-lab.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.1 kB (7%)

Content Size

887.1 kB

After Optimization

825.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eezeetags.com main page is 887.1 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. 45% of websites need less resources to load. Images take 782.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 41.8 kB

  • Original 52.4 kB
  • After minification 52.4 kB
  • After compression 10.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. 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 41.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 931 B

  • Original 782.1 kB
  • After minification 781.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. Eezeetags images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 13.3 kB

  • Original 27.1 kB
  • After minification 27.1 kB
  • After compression 13.8 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 13.3 kB or 49% of the original size.

CSS Optimization

-24%

Potential reduce by 6.1 kB

  • Original 25.6 kB
  • After minification 25.6 kB
  • After compression 19.5 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. Eezeetags.com needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (16%)

Requests Now

31

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eezeetags. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

eezeetags.com

eezeetags.com

304 ms

eezeetags.com

eezeetags.com

428 ms

style.css

style.css

191 ms

css

css

295 ms

manifest.js

manifest.js

281 ms

vendor.js

vendor.js

578 ms

app.js

app.js

482 ms

eezeetags

eezeetags

701 ms

gtm.js

gtm.js

136 ms

logo-eezeetags.svg

logo-eezeetags.svg

95 ms

icon-arrow.svg

icon-arrow.svg

93 ms

eezeetags-easy.png

eezeetags-easy.png

369 ms

eezeetags-fast.png

eezeetags-fast.png

514 ms

eezeetags-clean.png

eezeetags-clean.png

370 ms

icon-arrow-left.svg

icon-arrow-left.svg

272 ms

icon-arrow-right.svg

icon-arrow-right.svg

323 ms

icon-green-bullit.svg

icon-green-bullit.svg

364 ms

video-banner.jpg

video-banner.jpg

513 ms

rockwell-collins.jpg

rockwell-collins.jpg

372 ms

gatwick-south.png

gatwick-south.png

511 ms

self-bag-drop.png

self-bag-drop.png

511 ms

embross.jpg

embross.jpg

512 ms

self-tagging.png

self-tagging.png

514 ms

bagchain.jpg

bagchain.jpg

548 ms

tagomat.jpg

tagomat.jpg

553 ms

sick.jpg

sick.jpg

556 ms

bagpoint.png

bagpoint.png

557 ms

borry-vrieling.png

borry-vrieling.png

557 ms

helvetica_neue_75_bold.woff

helvetica_neue_75_bold.woff

575 ms

helvetica_neue_55_roman.woff

helvetica_neue_55_roman.woff

554 ms

u-lab-cookielaw.css

u-lab-cookielaw.css

254 ms

polyfills.promise.js

polyfills.promise.js

149 ms

provider.youtube.js

provider.youtube.js

14 ms

jwpsrv.js

jwpsrv.js

81 ms

related.js

related.js

81 ms

Accessibility Review

eezeetags.com accessibility score

95

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

eezeetags.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eezeetags.com SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eezeetags.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 Eezeetags.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.

Social Sharing Optimization

eezeetags.com

Open Graph data is detected on the main page of Eezeetags. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: