Tools & Wizards About Us
221e.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

221e.com

IMU, AI & Sensor Fusion | 221e™

Page Load Speed

21.6 sec in total

First Response

254 ms

Resources Loaded

20.5 sec

Page Rendered

869 ms

221e.com screenshot

About Website

Click here to check amazing 221 E content. Otherwise, check out these important facts you probably never knew about 221e.com

Add new superpowers to your smart device with 221e's IMU-based edge AI software and IoT sensors. We offer the best sensor fusion has to offer in health, PPE, and more.

Visit 221e.com

Key Findings

We analyzed 221e.com page load time and found that the first response time was 254 ms and then it took 21.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

221e.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value35.5 s

0/100

10%

TBT (Total Blocking Time)

Value4,020 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

221e.com

254 ms

221e.com

6073 ms

www.221e.com

3810 ms

wp-emoji-release.min.js

467 ms

style.min.css

562 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 89% of them (117 requests) were addressed to the original 221e.com, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Cdn.iubenda.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain 221e.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 942.3 kB (10%)

Content Size

9.5 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 221e.com main page is 9.5 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. 75% 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 8.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 347.9 kB

  • Original 401.6 kB
  • After minification 396.7 kB
  • After compression 53.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. 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 347.9 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 573.8 kB

  • Original 8.4 MB
  • After minification 7.8 MB

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. 221 E images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 14.9 kB

  • Original 557.5 kB
  • After minification 557.5 kB
  • After compression 542.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 5.8 kB

  • Original 191.2 kB
  • After minification 189.2 kB
  • After compression 185.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. 221e.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 81 (69%)

Requests Now

118

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

221e.com

221e.com

254 ms

221e.com

221e.com

6073 ms

www.221e.com

www.221e.com

3810 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

467 ms

style.min.css

style.min.css

562 ms

classic-themes.min.css

classic-themes.min.css

459 ms

styles.css

styles.css

463 ms

woocommerce-layout.css

woocommerce-layout.css

809 ms

woocommerce.css

woocommerce.css

950 ms

font-awesome-legacy.min.css

font-awesome-legacy.min.css

1506 ms

grid-system.css

grid-system.css

1477 ms

style.css

style.css

1444 ms

element-testimonial.css

element-testimonial.css

1480 ms

element-highlighted-text.css

element-highlighted-text.css

1496 ms

element-tabbed-section.css

element-tabbed-section.css

1509 ms

element-clients.css

element-clients.css

2130 ms

caroufredsel.css

caroufredsel.css

2157 ms

element-wpb-column-border.css

element-wpb-column-border.css

2153 ms

responsive.css

responsive.css

2528 ms

product-style-minimal.css

product-style-minimal.css

2446 ms

woocommerce.css

woocommerce.css

2610 ms

flickity.css

flickity.css

2546 ms

skin-material.css

skin-material.css

2560 ms

style.css

style.css

2643 ms

menu-dynamic.css

menu-dynamic.css

2762 ms

style_1.css

style_1.css

2864 ms

frontend.css

frontend.css

2873 ms

js_composer.min.css

js_composer.min.css

2870 ms

pum-site-styles.css

pum-site-styles.css

2921 ms

salient-dynamic-styles.css

salient-dynamic-styles.css

3066 ms

css

css

36 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

3035 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

3141 ms

wp-polyfill.min.js

wp-polyfill.min.js

3136 ms

hooks.min.js

hooks.min.js

3126 ms

w.js

w.js

24 ms

jquery.min.js

jquery.min.js

3311 ms

jquery-migrate.min.js

jquery-migrate.min.js

3523 ms

js.cookie.js

js.cookie.js

3570 ms

handl-utm-grabber.js

handl-utm-grabber.js

3581 ms

stub.js

stub.js

67 ms

iubenda_cs.js

iubenda_cs.js

50 ms

api.js

api.js

57 ms

style-non-critical.css

style-non-critical.css

3160 ms

woocommerce-non-critical.css

woocommerce-non-critical.css

3217 ms

jquery.fancybox.css

jquery.fancybox.css

3210 ms

core.css

core.css

3236 ms

slide-out-right-hover.css

slide-out-right-hover.css

3350 ms

wpm-public.p1.min.js

wpm-public.p1.min.js

3248 ms

email-decode.min.js

email-decode.min.js

2717 ms

index.js

index.js

2548 ms

index.js

index.js

2504 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

2526 ms

js.cookie.min.js

js.cookie.min.js

2520 ms

woocommerce.min.js

woocommerce.min.js

2992 ms

site_main.js

site_main.js

3047 ms

awdr-dynamic-price.js

awdr-dynamic-price.js

2424 ms

jquery.easing.min.js

jquery.easing.min.js

2402 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

2399 ms

priority.js

priority.js

2109 ms

transit.min.js

transit.min.js

2124 ms

waypoints.js

waypoints.js

2274 ms

imagesLoaded.min.js

imagesLoaded.min.js

2261 ms

hoverintent.min.js

hoverintent.min.js

2208 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

2273 ms

touchswipe.min.js

touchswipe.min.js

2062 ms

caroufredsel.min.js

caroufredsel.min.js

1930 ms

anime.min.js

anime.min.js

2236 ms

flickity.min.js

flickity.min.js

2356 ms

css

css

12 ms

superfish.js

superfish.js

2217 ms

init.js

init.js

2055 ms

scripts.js

scripts.js

2043 ms

frontend.js

frontend.js

2038 ms

js_composer_front.min.js

js_composer_front.min.js

2227 ms

g.gif

g.gif

13 ms

core.min.js

core.min.js

2036 ms

pum-site-scripts.js

pum-site-scripts.js

2259 ms

index.js

index.js

2071 ms

cart-fragments.min.js

cart-fragments.min.js

1956 ms

front-end.js

front-end.js

2224 ms

l5bau5vsdw

l5bau5vsdw

501 ms

gtm.js

gtm.js

443 ms

logo_colored.png

logo_colored.png

1598 ms

Logo.png

Logo.png

1680 ms

i_system.svg

i_system.svg

1706 ms

algorithms.svg

algorithms.svg

1832 ms

hardware.svg

hardware.svg

1847 ms

sensors.svg

sensors.svg

1916 ms

arm-3.png

arm-3.png

2009 ms

st-2.png

st-2.png

2012 ms

221e-logo-telit.png

221e-logo-telit.png

2103 ms

microchip-2.png

microchip-2.png

2101 ms

shutterstock_1568488030-1.png

shutterstock_1568488030-1.png

2525 ms

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbmyWQk8z_Q.ttf

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbmyWQk8z_Q.ttf

294 ms

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbouRQk8z_Q.ttf

8vIf7wUr0m80wwYf0QCXZzYzUoTK8RZQvRd-D1NYbouRQk8z_Q.ttf

295 ms

BlenderPro-Medium.woff

BlenderPro-Medium.woff

2057 ms

BlenderPro-Thin.woff

BlenderPro-Thin.woff

2273 ms

BlenderPro-Bold.woff

BlenderPro-Bold.woff

2222 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

3278 ms

OpenSans-SemiBold.woff

OpenSans-SemiBold.woff

2802 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

3374 ms

js

js

62 ms

clarity.js

clarity.js

29 ms

OpenSans-Light.woff

OpenSans-Light.woff

3316 ms

icomoon.woff

icomoon.woff

3177 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

2083 ms

shutterstock_735338710-1.png

shutterstock_735338710-1.png

3157 ms

shutterstock_507234181-1.png

shutterstock_507234181-1.png

3245 ms

Logo-VIKTOR-PNG.png

Logo-VIKTOR-PNG.png

3866 ms

2560px-Poste_italiane_logo.svg_.png

2560px-Poste_italiane_logo.svg_.png

3686 ms

fiberbow_logo.png

fiberbow_logo.png

3552 ms

logo_small.png

logo_small.png

2935 ms

Visa.svg

Visa.svg

3343 ms

Mastercard.svg

Mastercard.svg

3384 ms

PayPal.svg

PayPal.svg

2956 ms

YETI_Tavola-disegno-1.png

YETI_Tavola-disegno-1.png

3332 ms

infografica_sfondo.svg

infografica_sfondo.svg

3542 ms

shutterstock_2029416683-1.png

shutterstock_2029416683-1.png

3421 ms

shutterstock_1284976810-1.png

shutterstock_1284976810-1.png

3442 ms

shutterstock_276834887_MIN.jpg

shutterstock_276834887_MIN.jpg

3844 ms

recaptcha__en.js

recaptcha__en.js

28 ms

shutterstock_1721153281_MIN.jpg

shutterstock_1721153281_MIN.jpg

3883 ms

shutterstock_1851087646_MIN.jpg

shutterstock_1851087646_MIN.jpg

3808 ms

shutterstock_1979224544_MIN.jpg

shutterstock_1979224544_MIN.jpg

3840 ms

shutterstock_1025468848_MIN.jpg

shutterstock_1025468848_MIN.jpg

3403 ms

www.221e.com

www.221e.com

4206 ms

shutterstock_1144834865_MIN.jpg

shutterstock_1144834865_MIN.jpg

3580 ms

shutterstock_236262610_MIN.jpg

shutterstock_236262610_MIN.jpg

3803 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3070 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

309 ms

c.gif

c.gif

7 ms

Accessibility Review

221e.com accessibility score

88

Accessibility Issues

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.

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

221e.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

221e.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 221e.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 221e.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

221e.com

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