6.4 sec in total
251 ms
5.8 sec
319 ms
Visit longlife.co.uk now to see the best up-to-date Longlife content for United Kingdom and also check out these interesting facts you probably never knew about longlife.co.uk
Industry leading stainless steel, custom built exhausts. We can cater for any vehicle through our nationwide network - get a quote today from your local Longlife.
Visit longlife.co.ukWe analyzed Longlife.co.uk page load time and found that the first response time was 251 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
longlife.co.uk performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value17.9 s
0/100
25%
Value7.3 s
29/100
10%
Value220 ms
87/100
30%
Value0.269
45/100
15%
Value12.8 s
13/100
10%
251 ms
262 ms
2588 ms
477 ms
58 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 21% of them (18 requests) were addressed to the original Longlife.co.uk, 24% (20 requests) were made to Static.xx.fbcdn.net and 12% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Longlife.co.uk.
Page size can be reduced by 421.1 kB (47%)
898.7 kB
477.6 kB
In fact, the total size of Longlife.co.uk main page is 898.7 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. 70% of websites need less resources to load. Javascripts take 327.6 kB which makes up the majority of the site volume.
Potential reduce by 49.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 49.1 kB or 77% of the original size.
Potential reduce by 11.1 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. Longlife images are well optimized though.
Potential reduce by 139.9 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 139.9 kB or 43% of the original size.
Potential reduce by 221.0 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. Longlife.co.uk needs all CSS files to be minified and compressed as it can save up to 221.0 kB or 81% of the original size.
Number of requests can be reduced by 50 (67%)
75
25
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Longlife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
longlife.co.uk
251 ms
www.longlife.co.uk
262 ms
www.longlife.co.uk
2588 ms
main.min.css
477 ms
font-awesome.min.css
58 ms
modernizr.min.js
330 ms
jquery-1.11.2.min.js
68 ms
jquery-migrate-1.2.1.min.js
66 ms
jquery.typing-0.2.0.min.js
70 ms
ljy8lad.js
280 ms
jquery.cluetip.css
251 ms
jquery.cluetip.js
329 ms
element.js
96 ms
js
89 ms
scripts.min.js
1054 ms
cookies.php
419 ms
analytics.js
36 ms
mediaorb-footer-10-dark.png
624 ms
logo-longlife.png
102 ms
prestige.jpg
269 ms
your-vehicle_new.jpg
182 ms
performance_.jpg
183 ms
4x4.jpg
183 ms
replacements.jpg
441 ms
classic-vintage_.jpg
424 ms
www.longlife.co.uk
102 ms
translateelement.css
73 ms
main.js
98 ms
collect
36 ms
fontawesome-webfont.woff
3 ms
likebox.php
343 ms
124 ms
element_main.js
51 ms
GiTFCyW1-gC_gUz6aP8E0SUDOkmgg83YhsZUajaFSUJffH13gsMdeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
35 ms
K8T569KiNxpn5hHIyjrEjJUS26GTG8jQ7rTWxDB96pGffHV3gsMdeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
93 ms
jNCXjSKoDFMhTJg8rcXbGgZbKMIgc_b4QeQf7uKoC0jffHQ3gsMdeMJ6Mk6g5Mofb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
114 ms
oNZ69EhOwKv4JlOw83vuuMa8AHujlCU6FvXIkov4K29ffHn3gsMdeMJ6Mk6g5gBfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
248 ms
www-embed-player-vflfNyN_r.css
71 ms
www-embed-player.js
90 ms
base.js
110 ms
p.gif
417 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
59 ms
ad_status.js
63 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
82 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
83 ms
ebiMDO3r-8l.css
348 ms
jGc-59L_9lo.css
401 ms
k5BhlqovqZn.css
472 ms
q68gy-v_YMF.js
599 ms
FJmpeSpHpjS.js
697 ms
0wM5s1Khldu.js
536 ms
1bNoFZUdlYZ.js
536 ms
OloiM1PZafe.js
540 ms
LTv6ZK-5zxz.js
739 ms
1FCa-btixu2.js
717 ms
Oagsvfb4VWi.js
718 ms
pObvZSrFc_4.js
718 ms
HgJbVwzBr8E.js
717 ms
H3EKDTObx05.js
737 ms
OZFAYTv-ZUg.js
736 ms
cookies.css
48 ms
wait.gif
110 ms
index.php
479 ms
index.php
436 ms
translate_24dp.png
21 ms
l
44 ms
googlelogo_color_42x16dp.png
15 ms
Pin_Badge_normal.jpg
24 ms
12715228_974743119229481_6387395424987686650_n.jpg
342 ms
250310_203138399723294_4312502_n.jpg
411 ms
11011182_1613026622295352_5007359279740102881_n.jpg
479 ms
12019796_564941846994507_5078101627240021623_n.jpg
545 ms
306052_102198403314370_612331552_n.jpg
756 ms
12794591_10156556791825317_7398752710557630199_n.jpg
546 ms
11401370_10204651367351919_84983667687283014_n.jpg
546 ms
12105800_10207329161721059_1736562197286298931_n.jpg
619 ms
12065625_806610472799839_3393104048870447444_n.jpg
589 ms
10433950_1466749730269809_8895325680685181014_n.jpg
614 ms
wL6VQj7Ab77.png
78 ms
s7jcwEQH7Sx.png
79 ms
gxbPuQdXIZP.png
68 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
138 ms
nr-885.min.js
48 ms
363e793ca7
112 ms
longlife.co.uk accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
longlife.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
longlife.co.uk SEO score
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 Longlife.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 Longlife.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.
longlife.co.uk
Open Graph description is not detected on the main page of Longlife. 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: