Te.eg Site Title

Telecom Egypt Home

Te.eg Meta Description

Check telecom egypt new WE mobile packages ,mobile data bundles with best prices ,landline voice services, WE internet , Wifi, Vdsl, FTTH services with high speeds, Subscribe now

Te.eg Test Results

Te.eg Desktop Performance: 53/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 2,583 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Reduce initial server response time. Root document took 1,920 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Efficiently encode images. Potential savings of 1,240 KiB
Optimized images load faster and consume less cellular data. Learn more.
Eliminate render-blocking resources. Potential savings of 770 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Avoid multiple page redirects. Potential savings of 410 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Preload key requests. Potential savings of 350 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Reduce unused JavaScript. Potential savings of 277 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.
Reduce unused CSS. Potential savings of 102 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.
Properly size images. Potential savings of 100 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Serve static assets with an efficient cache policy
48 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid enormous network payloads
Total size was 4,380 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid an excessive DOM size
998 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
13 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
70 requests • 4,380 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.

Te.eg Desktop SEO: 82/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
2 links found
Descriptive link text helps search engines understand your content. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Te.eg Desktop Best Practices: 60/100
Quick overview:
General
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn more
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Trust and Safety
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Includes front-end JavaScript libraries with known security vulnerabilities
20 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Expected publicId to be an empty string
Te.eg Desktop Progressive Web App: 36/100
Quick overview:
PWA Optimized
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Te.eg Desktop Accessibility: 81/100
Quick overview:
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar tests
www.te.com
www.te.net
www.te.org
www.te.info
www.te.biz
www.te.us
www.te.mobi
www.e.eg
www.te.eg
www.re.eg
www.tre.eg
www.rte.eg
www.fe.eg
www.tfe.eg
www.fte.eg
www.ge.eg
www.tge.eg
www.gte.eg
www.ye.eg
www.tye.eg
www.yte.eg
www.t.eg
www.tw.eg
www.tew.eg
www.twe.eg
www.ts.eg
www.tes.eg
www.tse.eg
www.td.eg
www.ted.eg
www.tde.eg
www.tr.eg
www.ter.eg
Last Tested: