2.6 sec in total
109 ms
2.4 sec
120 ms
Visit pocketlandline.ee.co.uk now to see the best up-to-date Pocket Landline EE content for United Kingdom and also check out these interesting facts you probably never knew about pocketlandline.ee.co.uk
With EE Pocket Landline you can have all your calls diverted to your mobile. Never miss a call again with EE business.
Visit pocketlandline.ee.co.ukWe analyzed Pocketlandline.ee.co.uk page load time and found that the first response time was 109 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pocketlandline.ee.co.uk performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value6.0 s
13/100
25%
Value5.8 s
49/100
10%
Value160 ms
94/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
109 ms
92 ms
320 ms
381 ms
636 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 65% of them (32 requests) were addressed to the original Pocketlandline.ee.co.uk, 33% (16 requests) were made to Ee-nav.s3.amazonaws.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pocketlandline.ee.co.uk.
Page size can be reduced by 506.6 kB (53%)
961.6 kB
455.0 kB
In fact, the total size of Pocketlandline.ee.co.uk main page is 961.6 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. 25% of websites need less resources to load. Images take 547.4 kB which makes up the majority of the site volume.
Potential reduce by 59.2 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 11.3 kB, which is 17% 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 59.2 kB or 88% of the original size.
Potential reduce by 311.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. Obviously, Pocket Landline EE needs image optimization as it can save up to 311.7 kB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 54.0 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 54.0 kB or 22% of the original size.
Potential reduce by 81.7 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. Pocketlandline.ee.co.uk needs all CSS files to be minified and compressed as it can save up to 81.7 kB or 80% of the original size.
Number of requests can be reduced by 28 (62%)
45
17
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocket Landline EE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
signIn
109 ms
main.css
92 ms
jquery-3.4.1.js
320 ms
cookie.js
381 ms
jquery-ui.js
636 ms
jquery.bigframe.js
383 ms
jquery.cookie.js
383 ms
jquery.url.packed.js
382 ms
tooltip.jquery.js
411 ms
jquery.jplayer.min.js
471 ms
player.js
470 ms
AC_OETags.js
469 ms
javascript.js
472 ms
testHelper.js
497 ms
jquery.mousewheel.js
557 ms
mwheelIntent.js
560 ms
jquery.jscrollpane.min.js
559 ms
form.js
567 ms
wicket-ajax-jquery.js
590 ms
eehaf.min.js
294 ms
login_left.png
1113 ms
login_calls.png
547 ms
login_increase.png
546 ms
login_more.png
547 ms
login_grow.png
564 ms
primary_yellow.png
609 ms
login_right.png
618 ms
login.png
622 ms
ee_nobblee_boldwebfont.woff
544 ms
ee_nobblee_regularwebfont.woff
477 ms
jquery.min.js
22 ms
carots.png
136 ms
closeCookie.png
144 ms
checkbox.png
148 ms
modernizr.custom.js
81 ms
ee.master.menu.min.css
249 ms
templates.min.json
152 ms
ee.master.menu.min.js
97 ms
nav-icon-sprite.png
162 ms
header-social-icons.png
261 ms
sprite-link-arrows.png
311 ms
ee-logo1.png
301 ms
orange-logo.png
298 ms
orange-panel-close.png
308 ms
tmobile-logo-bg.gif
295 ms
tmobile-logo.gif
346 ms
tmobile-panel-close.png
394 ms
tmobile-content-bg.png
393 ms
social-icons.png
392 ms
pocketlandline.ee.co.uk accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pocketlandline.ee.co.uk 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pocketlandline.ee.co.uk 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 Pocketlandline.ee.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 Pocketlandline.ee.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.
pocketlandline.ee.co.uk
Open Graph description is not detected on the main page of Pocket Landline EE. 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: