Tools & Wizards About Us
eecard.co.uk screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

eecard.co.uk

Superfast 5G & 4G Phones, Tablets and Fibre Broadband | EE

Page Load Speed

5.9 sec in total

First Response

325 ms

Resources Loaded

3.7 sec

Page Rendered

1.9 sec

eecard.co.uk screenshot

About Website

Welcome to eecard.co.uk homepage info - get ready to check EE Card best content right away, or after learning these important things about eecard.co.uk

We're EE, the UK's No. 1 network with superfast 5G and 4G. Discover the best mobile phone, sim and fibre home broadband deals.

Visit eecard.co.uk

Key Findings

We analyzed Eecard.co.uk page load time and found that the first response time was 325 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

eecard.co.uk performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value4,250 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value43.4 s

0/100

10%

Network Requests Diagram

eecard.co.uk

325 ms

ee.co.uk

526 ms

ruxitagentjs_ICA7NQVfghqrux_10297240712040816.js

313 ms

global-elements.css

392 ms

index.css

407 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eecard.co.uk, 91% (69 requests) were made to Ee.co.uk and 5% (4 requests) were made to Zr.ee.co.uk. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Ee.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (16%)

Content Size

7.3 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eecard.co.uk main page is 7.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 438.1 kB

  • Original 584.2 kB
  • After minification 584.1 kB
  • After compression 146.1 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 438.1 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 735.1 kB

  • Original 6.4 MB
  • After minification 5.7 MB

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, EE Card needs image optimization as it can save up to 735.1 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

-0%

Potential reduce by 216 B

  • Original 204.6 kB
  • After minification 204.6 kB
  • After compression 204.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 811 B

  • Original 92.3 kB
  • After minification 92.3 kB
  • After compression 91.4 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. Eecard.co.uk has all CSS files already compressed.

Requests Breakdown

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

Requests Now

68

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eecard.co.uk

eecard.co.uk

325 ms

ee.co.uk

ee.co.uk

526 ms

ruxitagentjs_ICA7NQVfghqrux_10297240712040816.js

ruxitagentjs_ICA7NQVfghqrux_10297240712040816.js

313 ms

global-elements.css

global-elements.css

392 ms

index.css

index.css

407 ms

launch-ENc69d733bf4824e17ac296b1064825816.min.js

launch-ENc69d733bf4824e17ac296b1064825816.min.js

38 ms

ee_core_spa.min.css

ee_core_spa.min.css

706 ms

b2477c69a7020c3a.css

b2477c69a7020c3a.css

405 ms

6069c27829caa3cc.css

6069c27829caa3cc.css

298 ms

a3f220f3a3b733e8.css

a3f220f3a3b733e8.css

310 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

496 ms

webpack-2829e10e03926968.js

webpack-2829e10e03926968.js

429 ms

framework-58d9807ac049bfbd.js

framework-58d9807ac049bfbd.js

502 ms

main-5e0b48010fed7020.js

main-5e0b48010fed7020.js

494 ms

_app-41b9853de994f8dc.js

_app-41b9853de994f8dc.js

954 ms

8da61af5-816c3cd67610746a.js

8da61af5-816c3cd67610746a.js

589 ms

58ebb107-9ee67fe85d649ac5.js

58ebb107-9ee67fe85d649ac5.js

506 ms

9391-67a32c592f853a2b.js

9391-67a32c592f853a2b.js

592 ms

7760-bc2171d35b2dcd22.js

7760-bc2171d35b2dcd22.js

595 ms

9430-7b63abefcf9f51b7.js

9430-7b63abefcf9f51b7.js

698 ms

9959-54c62999e2af5b91.js

9959-54c62999e2af5b91.js

605 ms

6741-3f11c562df5b33b7.js

6741-3f11c562df5b33b7.js

685 ms

5853-34e12363773798ad.js

5853-34e12363773798ad.js

694 ms

homepage-2347c154a8fd6fac.js

homepage-2347c154a8fd6fac.js

698 ms

_buildManifest.js

_buildManifest.js

713 ms

_ssgManifest.js

_ssgManifest.js

783 ms

clientlibs_all.min.css

clientlibs_all.min.css

790 ms

clientlibs_shop.min.css

clientlibs_shop.min.css

795 ms

jquery.min.js

jquery.min.js

30 ms

ee_core_spa.min.js

ee_core_spa.min.js

672 ms

underscore.min.js

underscore.min.js

939 ms

clientlibs_spa.min.js

clientlibs_spa.min.js

946 ms

clientlibs_shop.min.js

clientlibs_shop.min.js

944 ms

webApplicationInjector.js

webApplicationInjector.js

1010 ms

ee_lazy_spa.min.css

ee_lazy_spa.min.css

775 ms

_Incapsula_Resource

_Incapsula_Resource

1010 ms

Apple_iPhone_16_Pro_Desktop_Homepage_Hero_1750x750.png

Apple_iPhone_16_Pro_Desktop_Homepage_Hero_1750x750.png

430 ms

Apple_iPhone_16_Pro_Mobile_Homepage_Hero_960x540.png

Apple_iPhone_16_Pro_Mobile_Homepage_Hero_960x540.png

432 ms

ee_one_new_desktop_homepage_hero_1750x750.png

ee_one_new_desktop_homepage_hero_1750x750.png

702 ms

ee_one_mobile_homepage_hero_960x540.png

ee_one_mobile_homepage_hero_960x540.png

905 ms

home-hero-1750-750px.jpg

home-hero-1750-750px.jpg

994 ms

home-hero-960-540px.jpg

home-hero-960-540px.jpg

992 ms

Google_HP_banner_Desktop_Homepage_Hero_1750x750.png

Google_HP_banner_Desktop_Homepage_Hero_1750x750.png

525 ms

Google_HP_banner_Mobile_Homepage_Hero_960x540.png

Google_HP_banner_Mobile_Homepage_Hero_960x540.png

522 ms

EE-HP_Hero_TV_1750x750.png

EE-HP_Hero_TV_1750x750.png

631 ms

EE-HP_Hero_TV_960x540.png

EE-HP_Hero_TV_960x540.png

626 ms

GameDayHero_1750x750.png

GameDayHero_1750x750.png

731 ms

GameDay_960x540.png

GameDay_960x540.png

732 ms

Apple_Welcome_to_EE_800x800.png

Apple_Welcome_to_EE_800x800.png

988 ms

google-pixel9proxl-welcome-to-ee-800x800.png

google-pixel9proxl-welcome-to-ee-800x800.png

864 ms

Samsung_Chromebook_GWP_Welcome_to_EE_800x800.png

Samsung_Chromebook_GWP_Welcome_to_EE_800x800.png

863 ms

ULData_EE_800x800.png

ULData_EE_800x800.png

931 ms

BoB_Welcome_to_EE_800x800.png

BoB_Welcome_to_EE_800x800.png

936 ms

Connected_Welcome_to_EE_800x800.png

Connected_Welcome_to_EE_800x800.png

1101 ms

MAC.png

MAC.png

1037 ms

bb-bau-welcome-to-ee-1546-800.jpg

bb-bau-welcome-to-ee-1546-800.jpg

1083 ms

FORO-xla-1200x600.png

FORO-xla-1200x600.png

1083 ms

Phones_Mobile_Card_1546x800.jpg

Phones_Mobile_Card_1546x800.jpg

1087 ms

Apple_TV_Mobile_WtEE_1546x800.jpg

Apple_TV_Mobile_WtEE_1546x800.jpg

1187 ms

Game_Day_2024_Gaming_Tile_Mobile_1546x800.jpg

Game_Day_2024_Gaming_Tile_Mobile_1546x800.jpg

1200 ms

standalone-400x300.png

standalone-400x300.png

1668 ms

GameSmart_Trending.jpg

GameSmart_Trending.jpg

1284 ms

PhoneSmart_Trending.jpg

PhoneSmart_Trending.jpg

1300 ms

LearnSmartV2_400x300.jpg

LearnSmartV2_400x300.jpg

1530 ms

EE-BT-tile.png

EE-BT-tile.png

1672 ms

Stay-connected.png

Stay-connected.png

1496 ms

Trending-eSIM_4x3_400x300_47kb.jpg

Trending-eSIM_4x3_400x300_47kb.jpg

1286 ms

EE_5G_Card_DMEE_400x300.jpg

EE_5G_Card_DMEE_400x300.jpg

1301 ms

Dottee-Light.1bb8dc7e.woff

Dottee-Light.1bb8dc7e.woff

1388 ms

Dottee-Regular.1c9a5814.woff

Dottee-Regular.1c9a5814.woff

1427 ms

Dottee-Bold.73223d8b.woff

Dottee-Bold.73223d8b.woff

1425 ms

sprite.symbol.svg

sprite.symbol.svg

469 ms

Non-Dottee-Regular.4b74b0e3.woff

Non-Dottee-Regular.4b74b0e3.woff

1320 ms

Non-Dottee-Light.94cad898.woff

Non-Dottee-Light.94cad898.woff

1324 ms

Non-Dottee-Bold.4204c340.woff

Non-Dottee-Bold.4204c340.woff

1319 ms

_Incapsula_Resource

_Incapsula_Resource

1232 ms

Accessibility Review

eecard.co.uk accessibility score

96

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

Best Practices

eecard.co.uk 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

eecard.co.uk 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 Eecard.co.uk 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 Eecard.co.uk 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

eecard.co.uk

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