10.3 sec in total
441 ms
9.3 sec
559 ms
Welcome to te.eg homepage info - get ready to check Te best content for Egypt right away, or after learning these important things about te.eg
اكتشف خدمات WE مصر للإنترنت المنزلي وباقات الموبايل والإنترنت فائق السرعة ودفع الفواتير والشحن أونلاين وأحدث العروض.
Visit te.egWe analyzed Te.eg page load time and found that the first response time was 441 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
te.eg performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value16.7 s
0/100
25%
Value13.3 s
2/100
10%
Value1,890 ms
9/100
30%
Value0.557
13/100
15%
Value26.3 s
0/100
10%
441 ms
1077 ms
415 ms
550 ms
414 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 62% of them (49 requests) were addressed to the original Te.eg, 14% (11 requests) were made to Developer.livehelpnow.net and 4% (3 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Te.eg.
Page size can be reduced by 525.3 kB (21%)
2.5 MB
2.0 MB
In fact, the total size of Te.eg main page is 2.5 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 158.6 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 39.6 kB, which is 21% 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 158.6 kB or 82% of the original size.
Potential reduce by 681 B
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. Te images are well optimized though.
Potential reduce by 169.8 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 169.8 kB or 53% of the original size.
Potential reduce by 196.2 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. Te.eg needs all CSS files to be minified and compressed as it can save up to 196.2 kB or 78% of the original size.
Number of requests can be reduced by 44 (57%)
77
33
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Te. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
Personal
441 ms
mashup:ra:collection
1077 ms
ra:collection
415 ms
vendor.css
550 ms
fix-style.css
414 ms
main.css
692 ms
add-style.css
414 ms
branding.css
555 ms
font-awesome.css
690 ms
vendor.js
1302 ms
main.js
688 ms
MainSliderDataLayer.js
692 ms
methods.js
827 ms
ra:collection
563 ms
ra:collection
575 ms
jquery-ui.js
43 ms
jquery-ui.css
40 ms
css
59 ms
droidarabickufi.css
69 ms
lang-icon.png
191 ms
mobile-menu-icon.png
190 ms
logo.png
191 ms
blank.gif
189 ms
triangle.png
190 ms
img4.jpg
189 ms
1700x651-en_preview.png
1288 ms
1700x651+%281%29+%281%29.png
2240 ms
English-Homepage-Banner-1700Wx651H.jpg
4835 ms
English-Homepage-Banner-1700Wx651H.jpg
928 ms
Homepage-Banner-1700Wx651H-En.jpg
1652 ms
English-Homepage-Banner-1700Wx651H.jpg
3547 ms
Bill+Reminder+1700Wx651H+%2817-10-17%29.jpg
2253 ms
World-Cup-Promo-1700Wx651H-Link-english.jpg
6465 ms
12%2BPiasters%2BHomepage%2BSpecial%2BPromotion%2BBanner%2B350Wx350H%2BEn%2B%2818-9-17%29.jpg.jpeg
1813 ms
Devices-350Wx350H-EN-2Oct.jpg
2076 ms
English%2BHomepage%2BSpecial%2BPromotion%2BBanner%2B350Wx350H.JPG.jpeg
2493 ms
Detailed%2BBill%2BHomepage%2BSpecial%2BPromotion%2BBanner%2B350Wx350H%2B%2814-9-17%29.jpg
3106 ms
140_banner+.jpg
2531 ms
Homepage%2BSpecial%2BPromotion%2BBanner%2B350Wx350H%2B%2815-9-17%29.jpg
2770 ms
Ma3ak_350pix-Wx350pix-H%2B%2817-9-17%29.jpg
2675 ms
3-piasters_350pix-Wx350pix-H.JPG.jpeg
2954 ms
icon-dotmasr.png
2908 ms
icon-m3ak.png
3033 ms
icon-faq.png
3079 ms
store-locator.png
3171 ms
gtm.js
169 ms
slide-2.jpg
3149 ms
next-white.svg
3148 ms
AvantGardeITCbyBT-Book.woff
3138 ms
fontawesome-webfont.woff
4387 ms
analytics.js
684 ms
conversion_async.js
704 ms
uwt.js
684 ms
fbevents.js
289 ms
lhn-jssdk-current.min.js
606 ms
ui-bg_flat_75_ffffff_40x100.png
77 ms
identity.js
28 ms
621027548100709
138 ms
blank.gif
2484 ms
back.svg
2543 ms
next.svg
2601 ms
flexslider-icon.woff
2678 ms
adsct
341 ms
102 ms
collect
160 ms
116 ms
lhn-jquery-1.11.0.min.js
221 ms
29 ms
51 ms
default.css
139 ms
opensans.css
142 ms
button.css
172 ms
hoc.css
215 ms
button-minimizer.svg
40 ms
button-closer.svg
38 ms
19 ms
192 ms
socket.js
29 ms
adsct
77 ms
te.eg accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
te.eg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
te.eg SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Te.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 Te.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.
te.eg
Open Graph description is not detected on the main page of Te. 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: