Tools & Wizards About Us
e-bee.com screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

e-bee.com

Page Load Speed

2.3 sec in total

First Response

111 ms

Resources Loaded

1.9 sec

Page Rendered

346 ms

e-bee.com screenshot

About Website

Visit e-bee.com now to see the best up-to-date E Bee content for India and also check out these interesting facts you probably never knew about e-bee.com

A robust centralised technology suite, proven to deliver successful commerce e-bee solutions   Why e-bee Watch Video View our story B2C Commerce Engage with your customers B2C Commerce B2B Commerce Au...

Visit e-bee.com

Key Findings

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

Performance Metrics

e-bee.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

www.e-bee.com

111 ms

style.css

28 ms

mobile-all.css

41 ms

xyz_cfm_shortcode_style.css

41 ms

jquery-ui.css

33 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 74% of them (71 requests) were addressed to the original E-bee.com, 10% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Share.lrcontent.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain E-bee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 495.2 kB (55%)

Content Size

900.1 kB

After Optimization

404.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-bee.com main page is 900.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. 65% of websites need less resources to load. Javascripts take 376.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 59.6 kB

  • Original 73.5 kB
  • After minification 72.1 kB
  • After compression 13.9 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 59.6 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 24.5 kB

  • Original 232.3 kB
  • After minification 207.8 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, E Bee needs image optimization as it can save up to 24.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 254.9 kB

  • Original 376.2 kB
  • After minification 368.9 kB
  • After compression 121.3 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 254.9 kB or 68% of the original size.

CSS Optimization

-72%

Potential reduce by 156.1 kB

  • Original 218.0 kB
  • After minification 197.2 kB
  • After compression 61.9 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-bee.com needs all CSS files to be minified and compressed as it can save up to 156.1 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (60%)

Requests Now

83

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.e-bee.com

www.e-bee.com

111 ms

style.css

style.css

28 ms

mobile-all.css

mobile-all.css

41 ms

xyz_cfm_shortcode_style.css

xyz_cfm_shortcode_style.css

41 ms

jquery-ui.css

jquery-ui.css

33 ms

nivoslider.css

nivoslider.css

50 ms

jcarousel.css

jcarousel.css

51 ms

style.css

style.css

51 ms

style.min.css

style.min.css

65 ms

loginradius_sharing_style.css

loginradius_sharing_style.css

71 ms

tab.min.css

tab.min.css

63 ms

dynamic-style.php

dynamic-style.php

103 ms

page-list.css

page-list.css

67 ms

pagenavi-css.css

pagenavi-css.css

68 ms

jquery.js

jquery.js

94 ms

jquery-migrate.min.js

jquery-migrate.min.js

95 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

90 ms

flowplayer-3.2.11.min.js

flowplayer-3.2.11.min.js

125 ms

jquery.minitwitter.js

jquery.minitwitter.js

127 ms

nivoslider.js

nivoslider.js

128 ms

jcarousel.js

jcarousel.js

128 ms

init.js

init.js

130 ms

script.min.js

script.min.js

131 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

130 ms

jquery.ui.mouse.min.js

jquery.ui.mouse.min.js

130 ms

jquery.ui.sortable.min.js

jquery.ui.sortable.min.js

133 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

133 ms

loginradius_sharing_admin.js

loginradius_sharing_admin.js

135 ms

loginradius_sharing.js

loginradius_sharing.js

133 ms

LoginRadius.js

LoginRadius.js

132 ms

dropdown-menu.js

dropdown-menu.js

141 ms

mobile-menu.js

mobile-menu.js

140 ms

jquery.min.js

jquery.min.js

169 ms

skdslider.min.js

skdslider.min.js

1177 ms

es-widget.css

es-widget.css

140 ms

es-widget.js

es-widget.js

139 ms

jquery.ui.datepicker.min.js

jquery.ui.datepicker.min.js

140 ms

back-to-top.js

back-to-top.js

140 ms

css

css

23 ms

comment-reply.min.js

comment-reply.min.js

139 ms

style.css

style.css

56 ms

dynamic-style.php

dynamic-style.php

51 ms

logo.png

logo.png

53 ms

menu_a_line.png

menu_a_line.png

51 ms

menu_a_bg.png

menu_a_bg.png

51 ms

multi-channel-web-ecommerce.jpg

multi-channel-web-ecommerce.jpg

52 ms

icon-video.png

icon-video.png

57 ms

icon-b2c.png

icon-b2c.png

58 ms

icon-b2b.png

icon-b2b.png

59 ms

icon-mobile.png

icon-mobile.png

69 ms

icon-isolutions.png

icon-isolutions.png

67 ms

icon-crm.png

icon-crm.png

68 ms

icon-social-integration.png

icon-social-integration.png

68 ms

icon-central-loyalty.png

icon-central-loyalty.png

69 ms

icon-offers-promotion.png

icon-offers-promotion.png

70 ms

icon-supplier-extranet.png

icon-supplier-extranet.png

73 ms

icon-call-centre.png

icon-call-centre.png

70 ms

icon-predictive-analysis.png

icon-predictive-analysis.png

74 ms

icon-business-process-mapping.png

icon-business-process-mapping.png

72 ms

icon-logistics.png

icon-logistics.png

73 ms

image003.png

image003.png

76 ms

image004.png

image004.png

76 ms

image005.png

image005.png

76 ms

image006.png

image006.png

76 ms

image007.png

image007.png

77 ms

image008.png

image008.png

78 ms

arrow-down.png

arrow-down.png

135 ms

bg-footer.png

bg-footer.png

10 ms

dynamic-style.php

dynamic-style.php

132 ms

analytics.js

analytics.js

65 ms

logo.png

logo.png

16 ms

all.js

all.js

14 ms

in.js

in.js

13 ms

platform.js

platform.js

82 ms

white-bg.png

white-bg.png

69 ms

enterprise-mobility-solutions.jpg

enterprise-mobility-solutions.jpg

73 ms

current-applications.jpg

current-applications.jpg

78 ms

back.png

back.png

77 ms

next.png

next.png

76 ms

to_top.png

to_top.png

67 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

64 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

65 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

64 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

65 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

67 ms

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf

65 ms

PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf

PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf

64 ms

PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf

PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf

65 ms

PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf

PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf

63 ms

PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf

PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf

64 ms

collect

collect

47 ms

secureAnonymousFramework

secureAnonymousFramework

110 ms

222 ms

xd_arbiter.php

xd_arbiter.php

63 ms

xd_arbiter.php

xd_arbiter.php

75 ms

ping

ping

58 ms

Accessibility Review

e-bee.com accessibility score

86

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

e-bee.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

e-bee.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-bee.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that E-bee.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

e-bee.com

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