Tools & Wizards About Us
we2.webeye.eu screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    48% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

we2.webeye.eu

WebEye | Complete telematics solutions from one provider

Page Load Speed

8.2 sec in total

First Response

499 ms

Resources Loaded

5.1 sec

Page Rendered

2.5 sec

we2.webeye.eu screenshot

About Website

Click here to check amazing We 2 Web Eye content for Romania. Otherwise, check out these important facts you probably never knew about we2.webeye.eu

We help our customers to organize their logistics processes more efficiently, cut operational costs and manage their workforce more economically.

Visit we2.webeye.eu

Key Findings

We analyzed We2.webeye.eu page load time and found that the first response time was 499 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

we2.webeye.eu performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

we2.webeye.eu

499 ms

we2.webeye.eu

517 ms

www.webeye.eu

1264 ms

gtm.js

77 ms

bootstrap.min.css

627 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original We2.webeye.eu, 79% (44 requests) were made to Webeye.eu and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Webeye.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 595.3 kB (48%)

Content Size

1.2 MB

After Optimization

637.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of We2.webeye.eu main page is 1.2 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. 55% of websites need less resources to load. Images take 639.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 29.3 kB

  • Original 36.6 kB
  • After minification 28.1 kB
  • After compression 7.3 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 8.4 kB, which is 23% 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 29.3 kB or 80% of the original size.

Image Optimization

-23%

Potential reduce by 144.3 kB

  • Original 639.5 kB
  • After minification 495.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. Obviously, We 2 Web Eye needs image optimization as it can save up to 144.3 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 177.8 kB

  • Original 266.2 kB
  • After minification 217.9 kB
  • After compression 88.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 177.8 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 243.9 kB

  • Original 290.5 kB
  • After minification 258.7 kB
  • After compression 46.6 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. We2.webeye.eu needs all CSS files to be minified and compressed as it can save up to 243.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (43%)

Requests Now

49

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

we2.webeye.eu

we2.webeye.eu

499 ms

we2.webeye.eu

we2.webeye.eu

517 ms

www.webeye.eu

www.webeye.eu

1264 ms

gtm.js

gtm.js

77 ms

bootstrap.min.css

bootstrap.min.css

627 ms

fontawesome.css

fontawesome.css

855 ms

slick.css

slick.css

655 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

652 ms

style.css

style.css

832 ms

core.css

core.css

643 ms

cookie-manager.css

cookie-manager.css

749 ms

webeye-eurowag-logo.svg

webeye-eurowag-logo.svg

749 ms

icon-menu.svg

icon-menu.svg

737 ms

jquery.min.js

jquery.min.js

1001 ms

popper.min.js

popper.min.js

858 ms

bootstrap.min.js

bootstrap.min.js

1561 ms

slick.min.js

slick.min.js

1001 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1544 ms

script.js

script.js

998 ms

core.js

core.js

1001 ms

analytics.js

analytics.js

62 ms

lftracker_v1_lYNOR8xnJKO4WQJZ.js

lftracker_v1_lYNOR8xnJKO4WQJZ.js

359 ms

collect

collect

43 ms

collect

collect

46 ms

map-bg.png

map-bg.png

1069 ms

map-bulgaria.png

map-bulgaria.png

1082 ms

map-czech.png

map-czech.png

1093 ms

map-croatia.png

map-croatia.png

1088 ms

map-germany.png

map-germany.png

1097 ms

map-hungary.png

map-hungary.png

1104 ms

map-poland.png

map-poland.png

1109 ms

map-portugal.png

map-portugal.png

1114 ms

map-romania.png

map-romania.png

1117 ms

map-slovakia.png

map-slovakia.png

1126 ms

map-slovenia.png

map-slovenia.png

1130 ms

map-ukraine.png

map-ukraine.png

1136 ms

multiplatform-lvhome1-EN.png

multiplatform-lvhome1-EN.png

1965 ms

icon-3-5-tonna.svg

icon-3-5-tonna.svg

1140 ms

icon-arrow-right.svg

icon-arrow-right.svg

1200 ms

icon-kisteherauto.svg

icon-kisteherauto.svg

1201 ms

icon-vegyesflotta.svg

icon-vegyesflotta.svg

1225 ms

flotta3.png

flotta3.png

1925 ms

timocom_new.jpg

timocom_new.jpg

1247 ms

daf.jpg

daf.jpg

1249 ms

ga-audiences

ga-audiences

119 ms

tr.lfeeder.com

tr.lfeeder.com

85 ms

gebruder.jpg

gebruder.jpg

1106 ms

jungheinrich.jpg

jungheinrich.jpg

1769 ms

logo-hrenko.svg

logo-hrenko.svg

1770 ms

icon-facebook.svg

icon-facebook.svg

1803 ms

icon-linkedin.svg

icon-linkedin.svg

1708 ms

css

css

51 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

901 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

862 ms

fa-solid-900.woff

fa-solid-900.woff

954 ms

fa-regular-400.woff

fa-regular-400.woff

955 ms

Accessibility Review

we2.webeye.eu accessibility score

85

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

we2.webeye.eu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

we2.webeye.eu SEO score

83

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 We2.webeye.eu 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 We2.webeye.eu 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

we2.webeye.eu

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