Tools & Wizards About Us
bee.com.eg screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

bee.com.eg

Bee Smart Payment Solutions | www.bee.com.eg - Home

Page Load Speed

3.6 sec in total

First Response

135 ms

Resources Loaded

3.3 sec

Page Rendered

169 ms

bee.com.eg screenshot

About Website

Welcome to bee.com.eg homepage info - get ready to check Bee best content for Egypt right away, or after learning these important things about bee.com.eg

Bee | www.bee.com.eg

Visit bee.com.eg

Key Findings

We analyzed Bee.com.eg page load time and found that the first response time was 135 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

bee.com.eg performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.189

65/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

bee.com.eg

135 ms

194 ms

font-awesome-5.min.css

25 ms

font-awesome-v4-shims.css

24 ms

animate.min.css

21 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 65% of them (37 requests) were addressed to the original Bee.com.eg, 21% (12 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Analytics.bee.com.eg.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.5 kB (18%)

Content Size

397.0 kB

After Optimization

324.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bee.com.eg main page is 397.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. 60% of websites need less resources to load. Javascripts take 173.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 29.1 kB

  • Original 35.8 kB
  • After minification 32.2 kB
  • After compression 6.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 29.1 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 2.6 kB

  • Original 51.1 kB
  • After minification 48.5 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. Bee images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 18.7 kB

  • Original 173.1 kB
  • After minification 173.1 kB
  • After compression 154.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 18.7 kB or 11% of the original size.

CSS Optimization

-16%

Potential reduce by 22.1 kB

  • Original 137.0 kB
  • After minification 137.0 kB
  • After compression 114.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. Bee.com.eg needs all CSS files to be minified and compressed as it can save up to 22.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (74%)

Requests Now

39

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 16 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

bee.com.eg

bee.com.eg

135 ms

194 ms

font-awesome-5.min.css

font-awesome-5.min.css

25 ms

font-awesome-v4-shims.css

font-awesome-v4-shims.css

24 ms

animate.min.css

animate.min.css

21 ms

sppagebuilder.css

sppagebuilder.css

38 ms

sppagecontainer.css

sppagecontainer.css

26 ms

jquery.smartbanner.css

jquery.smartbanner.css

26 ms

css

css

48 ms

css

css

66 ms

css

css

71 ms

bootstrap.min.css

bootstrap.min.css

29 ms

font-awesome.min.css

font-awesome.min.css

96 ms

template.css

template.css

89 ms

default.css

default.css

35 ms

magnific-popup.css

magnific-popup.css

36 ms

wk-styles-9c05a468.css

wk-styles-9c05a468.css

98 ms

jquery.min.js

jquery.min.js

97 ms

jquery-noconflict.js

jquery-noconflict.js

93 ms

jquery-migrate.min.js

jquery-migrate.min.js

95 ms

jquery.parallax.js

jquery.parallax.js

96 ms

sppagebuilder.js

sppagebuilder.js

121 ms

jquery.smartbanner.js

jquery.smartbanner.js

119 ms

popper.min.js

popper.min.js

119 ms

bootstrap.min.js

bootstrap.min.js

128 ms

main.js

main.js

119 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

120 ms

core.js

core.js

127 ms

uikit2-5a141b00.js

uikit2-5a141b00.js

188 ms

wk-scripts-dff797c8.js

wk-scripts-dff797c8.js

127 ms

kennsgab3riudwhts9dpujfruxjvercb.js

kennsgab3riudwhts9dpujfruxjvercb.js

164 ms

render.a0bf496f0204e303a7bd.js

render.a0bf496f0204e303a7bd.js

154 ms

fbevents.js

fbevents.js

132 ms

matomo.js

matomo.js

240 ms

logo-for-customer.png

logo-for-customer.png

19 ms

bee-logo-t.png

bee-logo-t.png

49 ms

home-icon-01.png

home-icon-01.png

18 ms

home-icon-021.png

home-icon-021.png

57 ms

home-icon-03.png

home-icon-03.png

17 ms

logo-bee3.png

logo-bee3.png

48 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

57 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

57 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

58 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

77 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

91 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

97 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

98 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

99 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

99 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

99 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

99 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

115 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

116 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

115 ms

fa-brands-400.woff

fa-brands-400.woff

56 ms

149 ms

matomo.php

matomo.php

1579 ms

Accessibility Review

bee.com.eg accessibility score

97

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

Links do not have a discernible name

Best Practices

bee.com.eg 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

bee.com.eg SEO score

99

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bee.com.eg can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it does not match the claimed English language. Our system also found out that Bee.com.eg 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

bee.com.eg

Open Graph description is not detected on the main page of Bee. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: