Tools & Wizards About Us
londoneye.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

londoneye.com

The lastminute.com London Eye: The Official Tickets Website

Page Load Speed

13.7 sec in total

First Response

931 ms

Resources Loaded

8.7 sec

Page Rendered

4.1 sec

londoneye.com screenshot

About Website

Welcome to londoneye.com homepage info - get ready to check London Eye best content for United Kingdom right away, or after learning these important things about londoneye.com

Discover one of the best London attractions, the lastminute.com London Eye. Book online for the best rate and guaranteed entry to one of the city's top attractions.

Visit londoneye.com

Key Findings

We analyzed Londoneye.com page load time and found that the first response time was 931 ms and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

londoneye.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.766

5/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

www.londoneye.com

931 ms

www.londoneye.com

562 ms

londoneye.css

381 ms

modernizr-2.6.2.min.js

494 ms

buttons.js

484 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 22% of them (16 requests) were addressed to the original Londoneye.com, 7% (5 requests) were made to Ws.sharethis.com and 6% (4 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Londoneye.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 637.9 kB (30%)

Content Size

2.1 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Londoneye.com main page is 2.1 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 68.0 kB

  • Original 82.9 kB
  • After minification 54.0 kB
  • After compression 14.9 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 28.9 kB, which is 35% 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 68.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 4.5 kB

  • Original 1.1 MB
  • After minification 1.1 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. London Eye images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 410.7 kB

  • Original 698.1 kB
  • After minification 670.9 kB
  • After compression 287.4 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 410.7 kB or 59% of the original size.

CSS Optimization

-84%

Potential reduce by 154.6 kB

  • Original 183.9 kB
  • After minification 183.5 kB
  • After compression 29.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. Londoneye.com needs all CSS files to be minified and compressed as it can save up to 154.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (62%)

Requests Now

65

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.londoneye.com

www.londoneye.com

931 ms

www.londoneye.com

www.londoneye.com

562 ms

londoneye.css

londoneye.css

381 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

494 ms

buttons.js

buttons.js

484 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

468 ms

jquery-ui.js

jquery-ui.js

744 ms

jquery.validate.min.js

jquery.validate.min.js

888 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

870 ms

opentag-125707-1951171.js

opentag-125707-1951171.js

479 ms

WidgetEmbed-cdsratingsonlynarrow

WidgetEmbed-cdsratingsonlynarrow

742 ms

jquery.min.js

jquery.min.js

794 ms

app.js

app.js

741 ms

conversion.js

conversion.js

611 ms

accesso.js

accesso.js

792 ms

fbevents.js

fbevents.js

308 ms

le_combi_01_600x300.jpg

le_combi_01_600x300.jpg

667 ms

tripadvisor_logo_transp_340x80-18034-2.png

tripadvisor_logo_transp_340x80-18034-2.png

957 ms

img_5315.jpg

img_5315.jpg

720 ms

champagne_experience_2_promo-image.jpg

champagne_experience_2_promo-image.jpg

870 ms

private_capsule_2_promo-image.jpg

private_capsule_2_promo-image.jpg

1264 ms

qtracker-v3-min.js

qtracker-v3-min.js

579 ms

smartserve-4052.js

smartserve-4052.js

1258 ms

proactive-feedback.js

proactive-feedback.js

701 ms

activityi;src=2630373;type=londo855;cat=new_l0;ord=1;num=2565343459136.784

activityi;src=2630373;type=londo855;cat=new_l0;ord=1;num=2565343459136.784

684 ms

logo-le-white.svg

logo-le-white.svg

644 ms

hero_mask.png

hero_mask.png

1946 ms

567 ms

2ABB98_0_0.woff

2ABB98_0_0.woff

739 ms

leicons.woff

leicons.woff

566 ms

2ABB98_1_0.woff

2ABB98_1_0.woff

1551 ms

cdswidget-ratingsonly-v21719610117b.css%20%27%29%3B

cdswidget-ratingsonly-v21719610117b.css%20%27%29%3B

5 ms

cdswidgets_m-c-v2102084671b.js

cdswidgets_m-c-v2102084671b.js

1650 ms

cdswidget-ratingsonly-v21719610117b.css

cdswidget-ratingsonly-v21719610117b.css

1738 ms

t2

t2

1997 ms

p-CewQPaFezVPaU.gif

p-CewQPaFezVPaU.gif

1552 ms

5437af3701896031d5de6565

5437af3701896031d5de6565

1936 ms

event

event

1526 ms

activity

activity

1959 ms

tag2

tag2

1488 ms

t2

t2

1487 ms

cc

cc

48 ms

skyline-le.svg

skyline-le.svg

358 ms

iframe_api

iframe_api

1022 ms

dc.js

dc.js

1123 ms

892_1600x1000_v2.jpg

892_1600x1000_v2.jpg

2650 ms

getAllAppDefault.esi

getAllAppDefault.esi

316 ms

2028.js

2028.js

246 ms

www-widgetapi.js

www-widgetapi.js

275 ms

253 ms

inpage_linkid.js

inpage_linkid.js

253 ms

s

s

234 ms

u

u

295 ms

getSegment.php

getSegment.php

387 ms

__utm.gif

__utm.gif

40 ms

img

img

35 ms

tag2

tag2

82 ms

t.dhj

t.dhj

97 ms

t.dhj

t.dhj

30 ms

hbpix

hbpix

244 ms

cm

cm

137 ms

s-3271.xgi

s-3271.xgi

6 ms

12 ms

64 ms

26751

26751

196 ms

xrefid.xgi

xrefid.xgi

8 ms

index.html

index.html

28 ms

buttons-secure.css

buttons-secure.css

36 ms

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

46 ms

st.1188278743c14064d5e8ae56c8ada29c.js

st.1188278743c14064d5e8ae56c8ada29c.js

85 ms

4.5.png

4.5.png

258 ms

shim.html

shim.html

258 ms

Accessibility Review

londoneye.com accessibility score

97

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

Heading elements are not in a sequentially-descending order

Best Practices

londoneye.com best practices score

83

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

Page has valid source maps

SEO Factors

londoneye.com SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Londoneye.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Londoneye.com 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

londoneye.com

Open Graph description is not detected on the main page of London Eye. 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: