Tools & Wizards About Us
sms.com.eg screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

sms.com.eg

SMS Misr | Bulk SMS | Send Branded SMS

Page Load Speed

1.7 sec in total

First Response

162 ms

Resources Loaded

942 ms

Page Rendered

593 ms

sms.com.eg screenshot

About Website

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

SMS Egypt , SMS Misr , BULK SMS , Mobile Advertising , LBA , API , SMS Verification , Create SMS Campaigns, Marketing Campaigns, Send Online SMS , Marketing , Location Based Advertising , Advertising ...

Visit sms.com.eg

Key Findings

We analyzed Sms.com.eg page load time and found that the first response time was 162 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

sms.com.eg performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

sms.com.eg

162 ms

sms.com.eg

108 ms

bootstrap.min.css

44 ms

owl.carousel.min.css

60 ms

owl.theme.default.min.css

73 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 54% of them (25 requests) were addressed to the original Sms.com.eg, 30% (14 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (432 ms) relates to the external source Embed.tawk.to.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.2 kB (28%)

Content Size

472.1 kB

After Optimization

340.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 38.5 kB

  • Original 43.0 kB
  • After minification 24.3 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 18.7 kB, which is 43% 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 38.5 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 22.7 kB
  • After minification 22.7 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. SMS images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 38.6 kB

  • Original 246.0 kB
  • After minification 246.0 kB
  • After compression 207.5 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 38.6 kB or 16% of the original size.

CSS Optimization

-34%

Potential reduce by 55.1 kB

  • Original 160.4 kB
  • After minification 160.4 kB
  • After compression 105.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. Sms.com.eg needs all CSS files to be minified and compressed as it can save up to 55.1 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (58%)

Requests Now

26

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sms.com.eg

sms.com.eg

162 ms

sms.com.eg

sms.com.eg

108 ms

bootstrap.min.css

bootstrap.min.css

44 ms

owl.carousel.min.css

owl.carousel.min.css

60 ms

owl.theme.default.min.css

owl.theme.default.min.css

73 ms

magnific-popup.min.css

magnific-popup.min.css

74 ms

sal.min.css

sal.min.css

78 ms

theme.css

theme.css

125 ms

bootstrap-icons.css

bootstrap-icons.css

82 ms

all.css

all.css

94 ms

jquery.min.js

jquery.min.js

107 ms

js

js

62 ms

polyfill.min.js

polyfill.min.js

33 ms

plugins.js

plugins.js

157 ms

functions.js

functions.js

102 ms

css

css

51 ms

css

css

71 ms

css

css

72 ms

1gja1r0j2

1gja1r0j2

432 ms

scevent.min.js

scevent.min.js

231 ms

curve.svg

curve.svg

218 ms

1-min.png

1-min.png

179 ms

2-min.png

2-min.png

180 ms

3-min.png

3-min.png

178 ms

4-min.png

4-min.png

177 ms

5-min.png

5-min.png

176 ms

6-min.png

6-min.png

179 ms

7-min.png

7-min.png

289 ms

8-min.png

8-min.png

288 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

32 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

100 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

137 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

138 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

136 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

136 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

136 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

137 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

138 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

140 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

138 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

140 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

139 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

137 ms

bootstrap-icons.woff

bootstrap-icons.woff

132 ms

fa-regular-400.ttf

fa-regular-400.ttf

131 ms

fa-solid-900.ttf

fa-solid-900.ttf

225 ms

Accessibility Review

sms.com.eg accessibility score

79

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

sms.com.eg SEO score

98

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sms.com.eg 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 Sms.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

sms.com.eg

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