Tools & Wizards About Us
flatland.london screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

flatland.london

Flatland London – Established 1971

Page Load Speed

4.9 sec in total

First Response

499 ms

Resources Loaded

2.4 sec

Page Rendered

2 sec

flatland.london screenshot

About Website

Visit flatland.london now to see the best up-to-date Flatland content and also check out these interesting facts you probably never knew about flatland.london

Visit flatland.london

Key Findings

We analyzed Flatland.london page load time and found that the first response time was 499 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

flatland.london performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

www.flatland.london

499 ms

wp-emoji-release.min.js

134 ms

style.min.css

200 ms

swpm.common.css

206 ms

style.css

297 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 82% of them (42 requests) were addressed to the original Flatland.london, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Crm.zohopublic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Flatland.london.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.4 kB (9%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flatland.london main page is 1.4 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 78.3 kB

  • Original 103.8 kB
  • After minification 90.8 kB
  • After compression 25.6 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 13.0 kB, which is 13% 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 78.3 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 31.8 kB

  • Original 1.2 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. Flatland images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 2.4 kB

  • Original 54.2 kB
  • After minification 54.2 kB
  • After compression 51.8 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

-18%

Potential reduce by 4.9 kB

  • Original 27.9 kB
  • After minification 27.6 kB
  • After compression 23.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. Flatland.london needs all CSS files to be minified and compressed as it can save up to 4.9 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (31%)

Requests Now

45

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.flatland.london

www.flatland.london

499 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

134 ms

style.min.css

style.min.css

200 ms

swpm.common.css

swpm.common.css

206 ms

style.css

style.css

297 ms

style.css

style.css

203 ms

css

css

44 ms

favorites.css

favorites.css

206 ms

jquery.js

jquery.js

242 ms

jquery-migrate.min.js

jquery-migrate.min.js

341 ms

favorites.min.js

favorites.min.js

343 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

399 ms

navigation.js

navigation.js

400 ms

global.js

global.js

466 ms

jquery.scrollTo.js

jquery.scrollTo.js

467 ms

wp-embed.min.js

wp-embed.min.js

468 ms

cropped-flat-.jpg

cropped-flat-.jpg

118 ms

cropped-FLATLAND-LOGO-BLACK.jpg

cropped-FLATLAND-LOGO-BLACK.jpg

551 ms

Pic-1-16.jpg

Pic-1-16.jpg

549 ms

Pic-1-1.jpg

Pic-1-1.jpg

559 ms

Pic-3-6.jpg

Pic-3-6.jpg

657 ms

Pic-1-36.jpg

Pic-1-36.jpg

570 ms

Pic-1-1.jpg

Pic-1-1.jpg

574 ms

Pic-1-6.jpg

Pic-1-6.jpg

740 ms

7025_1585325162_l.jpg

7025_1585325162_l.jpg

648 ms

7060_1591103562_l.jpg

7060_1591103562_l.jpg

660 ms

2815_1406285798_l.jpg

2815_1406285798_l.jpg

773 ms

Pic-1-39.jpg

Pic-1-39.jpg

780 ms

Pic-1-24.jpg

Pic-1-24.jpg

747 ms

Pic-1-3.jpg

Pic-1-3.jpg

852 ms

Pic-1-1.jpg

Pic-1-1.jpg

763 ms

Pic-1-2.jpg

Pic-1-2.jpg

933 ms

Pic-1.jpg

Pic-1.jpg

850 ms

Pic-1-33.jpg

Pic-1-33.jpg

865 ms

Pic-1-4.jpg

Pic-1-4.jpg

879 ms

6975_1572278830_l.jpg

6975_1572278830_l.jpg

885 ms

Pic-1-2.jpg

Pic-1-2.jpg

1049 ms

Pic-1.jpg

Pic-1.jpg

953 ms

Pic-1-1.jpg

Pic-1-1.jpg

966 ms

Pic-5-18.jpg

Pic-5-18.jpg

1087 ms

Pic-2-38.jpg

Pic-2-38.jpg

990 ms

Pic-1-11.jpg

Pic-1-11.jpg

1031 ms

Pic-1-34.jpg

Pic-1-34.jpg

1055 ms

flatland_button.png

flatland_button.png

1068 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkDtDM.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWkDtDM.ttf

88 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWkDtDM.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWkDtDM.ttf

127 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduh8MKkDtDM.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduh8MKkDtDM.ttf

140 ms

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhrsKkDtDM.ttf

jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhrsKkDtDM.ttf

139 ms

WebFormServeServlet

WebFormServeServlet

316 ms

CaptchaServlet

CaptchaServlet

83 ms

WebFormAnalyticsServeServlet

WebFormAnalyticsServeServlet

139 ms

Accessibility Review

flatland.london accessibility score

94

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

flatland.london 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

SEO Factors

flatland.london SEO score

92

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

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 Flatland.london 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 Flatland.london 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

flatland.london

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