Tools & Wizards About Us
e-we.co screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

e-we.co

eWe - The Shared Electric Scooter and Bike Mobility App

Page Load Speed

7.2 sec in total

First Response

782 ms

Resources Loaded

5.5 sec

Page Rendered

989 ms

e-we.co screenshot

About Website

Visit e-we.co now to see the best up-to-date EWe content and also check out these interesting facts you probably never knew about e-we.co

eWe is Indis's first EV centric shared mobility app- a platform where you can rent electric scooters and e-bikes on the go. It's fast, clean & economical and offers a solution to address all...

Visit e-we.co

Key Findings

We analyzed E-we.co page load time and found that the first response time was 782 ms and then it took 6.4 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

e-we.co performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

e-we.co

782 ms

wp-emoji-release.min.js

230 ms

sbi-styles.min.css

444 ms

style.min.css

671 ms

styles.css

458 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 65% of them (57 requests) were addressed to the original E-we.co, 20% (18 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain E-we.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.6 kB (27%)

Content Size

599.0 kB

After Optimization

434.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-we.co main page is 599.0 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. 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 251.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 42.6 kB

  • Original 53.1 kB
  • After minification 48.6 kB
  • After compression 10.5 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 42.6 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 14.3 kB

  • Original 139.6 kB
  • After minification 125.3 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. EWe images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 48.9 kB

  • Original 251.1 kB
  • After minification 250.9 kB
  • After compression 202.2 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 48.9 kB or 19% of the original size.

CSS Optimization

-38%

Potential reduce by 58.8 kB

  • Original 155.1 kB
  • After minification 138.7 kB
  • After compression 96.3 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. E-we.co needs all CSS files to be minified and compressed as it can save up to 58.8 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (88%)

Requests Now

65

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-we.co

e-we.co

782 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

230 ms

sbi-styles.min.css

sbi-styles.min.css

444 ms

style.min.css

style.min.css

671 ms

styles.css

styles.css

458 ms

settings.css

settings.css

459 ms

close-button-icon.css

close-button-icon.css

491 ms

YouTubePopUp.css

YouTubePopUp.css

502 ms

wonderplugincarouselengine.css

wonderplugincarouselengine.css

666 ms

bootstrap.css

bootstrap.css

899 ms

font-awesome.css

font-awesome.css

695 ms

flaticon.css

flaticon.css

737 ms

animate.css

animate.css

748 ms

owl.css

owl.css

888 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

892 ms

hover.css

hover.css

908 ms

gui.css

gui.css

984 ms

style.css

style.css

998 ms

custom.css

custom.css

1115 ms

gutenberg.css

gutenberg.css

1143 ms

responsive.css

responsive.css

1123 ms

css

css

53 ms

css

css

53 ms

kingcomposer.min.css

kingcomposer.min.css

1124 ms

animate.css

animate.css

1236 ms

flaticon.css

flaticon.css

1252 ms

icons.css

icons.css

1339 ms

jquery.min.js

jquery.min.js

1563 ms

jquery-migrate.min.js

jquery-migrate.min.js

1411 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1590 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1487 ms

YouTubePopUp.jquery.js

YouTubePopUp.jquery.js

1502 ms

YouTubePopUp.js

YouTubePopUp.js

1560 ms

wonderplugincarouselskins.js

wonderplugincarouselskins.js

1682 ms

wonderplugincarousel.js

wonderplugincarousel.js

1979 ms

js

js

58 ms

703.css

703.css

1752 ms

667.css

667.css

1783 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1775 ms

wp-polyfill.min.js

wp-polyfill.min.js

1788 ms

index.js

index.js

1595 ms

gmaps.js

gmaps.js

1734 ms

core.min.js

core.min.js

1726 ms

bootstrap.min.js

bootstrap.min.js

1726 ms

jquery.fancybox.js

jquery.fancybox.js

1699 ms

owl.js

owl.js

1687 ms

wow.js

wow.js

1792 ms

appear.js

appear.js

2004 ms

mixitup.js

mixitup.js

1800 ms

jquery.countdown.js

jquery.countdown.js

1761 ms

script.js

script.js

1931 ms

map-script.js

map-script.js

1793 ms

comment-reply.min.js

comment-reply.min.js

1789 ms

kingcomposer.min.js

kingcomposer.min.js

1729 ms

gen_204

gen_204

52 ms

css

css

48 ms

gtm.js

gtm.js

459 ms

email.png

email.png

1299 ms

footer-logo.png

footer-logo.png

427 ms

bannar-bg-1.png

bannar-bg-1.png

715 ms

banner-image-2.png

banner-image-2.png

1271 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

838 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

285 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

286 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

983 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

55 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

285 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

982 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

283 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

283 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

982 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

948 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

947 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

948 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

996 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

996 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

996 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

994 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

994 ms

fa-brands-400.woff

fa-brands-400.woff

1146 ms

flaticon.svg

flaticon.svg

1453 ms

flaticon.woff

flaticon.woff

801 ms

analytics.js

analytics.js

602 ms

insight.min.js

insight.min.js

597 ms

fbevents.js

fbevents.js

570 ms

collect

collect

339 ms

608939389701782

608939389701782

224 ms

22 ms

Accessibility Review

e-we.co accessibility score

63

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.

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

e-we.co best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

e-we.co 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 E-we.co 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 E-we.co 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

e-we.co

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