Tools & Wizards About Us
francis-barnett.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    47% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

francis-barnett.org

Francis-Barnett Coventry - Bringing Back The Francis Barnett Name

Page Load Speed

7.9 sec in total

First Response

710 ms

Resources Loaded

2.9 sec

Page Rendered

4.4 sec

francis-barnett.org screenshot

About Website

Welcome to francis-barnett.org homepage info - get ready to check Francis Barnett best content right away, or after learning these important things about francis-barnett.org

Francis-Barnett Coventry Provides New Motorbikes Made With The Classic British Design Of The Original Francis-Barnett bikes In Mind. Ready Build For You.

Visit francis-barnett.org

Key Findings

We analyzed Francis-barnett.org page load time and found that the first response time was 710 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

francis-barnett.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value3,620 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

francis-barnett.org

710 ms

styles.css

110 ms

embed

385 ms

font-awesome.min.css

193 ms

bootstrap-image-gallery.css

177 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 64% of them (85 requests) were addressed to the original Francis-barnett.org, 16% (21 requests) were made to Google.com and 9% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Francis-barnett.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 427.0 kB (5%)

Content Size

8.9 MB

After Optimization

8.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Francis-barnett.org main page is 8.9 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. 85% 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 8.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 46.9 kB

  • Original 54.6 kB
  • After minification 39.2 kB
  • After compression 7.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 15.3 kB, which is 28% 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 46.9 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 377.0 kB

  • Original 8.6 MB
  • After minification 8.3 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. Francis Barnett images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 132.2 kB
  • After minification 132.2 kB
  • After compression 130.5 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

-5%

Potential reduce by 1.3 kB

  • Original 23.5 kB
  • After minification 23.5 kB
  • After compression 22.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. Francis-barnett.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (17%)

Requests Now

127

After Optimization

105

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

francis-barnett.org

francis-barnett.org

710 ms

styles.css

styles.css

110 ms

embed

embed

385 ms

font-awesome.min.css

font-awesome.min.css

193 ms

bootstrap-image-gallery.css

bootstrap-image-gallery.css

177 ms

blueimp-gallery.min.css

blueimp-gallery.min.css

58 ms

jquery-1.10.2.js

jquery-1.10.2.js

349 ms

bootstrap.min.js

bootstrap.min.js

61 ms

jquery.blueimp-gallery.min.js

jquery.blueimp-gallery.min.js

75 ms

bootstrap-image-gallery.js

bootstrap-image-gallery.js

221 ms

demo.js

demo.js

339 ms

ebike1.jpg

ebike1.jpg

374 ms

ebike2.jpg

ebike2.jpg

404 ms

ebike4.jpg

ebike4.jpg

482 ms

2.jpg

2.jpg

678 ms

7.jpg

7.jpg

827 ms

13.jpg

13.jpg

681 ms

10.jpg

10.jpg

679 ms

8.jpg

8.jpg

671 ms

6.jpg

6.jpg

903 ms

5.jpg

5.jpg

904 ms

5.jpg

5.jpg

803 ms

4.jpg

4.jpg

801 ms

6.jpg

6.jpg

799 ms

7.jpg

7.jpg

802 ms

4.jpg

4.jpg

875 ms

1.jpg

1.jpg

882 ms

2.jpg

2.jpg

900 ms

3.jpg

3.jpg

884 ms

5.jpg

5.jpg

992 ms

4.jpg

4.jpg

1018 ms

6.jpg

6.jpg

964 ms

7.jpg

7.jpg

965 ms

8.jpg

8.jpg

978 ms

1.jpg

1.jpg

979 ms

2.jpg

2.jpg

1060 ms

3.jpg

3.jpg

1067 ms

FB1040.jpg

FB1040.jpg

1094 ms

10.jpg

10.jpg

1068 ms

9.jpg

9.jpg

1103 ms

7.jpg

7.jpg

1105 ms

4.jpg

4.jpg

1058 ms

9.jpg

9.jpg

1002 ms

1.jpg

1.jpg

957 ms

11.jpg

11.jpg

849 ms

analytics.js

analytics.js

43 ms

2.jpg

2.jpg

856 ms

js

js

68 ms

12.jpg

12.jpg

859 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

891 ms

bikeg.jpg

bikeg.jpg

875 ms

collect

collect

58 ms

gen_204

gen_204

24 ms

init_embed.js

init_embed.js

60 ms

FBhires051s.jpg

FBhires051s.jpg

799 ms

collect

collect

186 ms

common.js

common.js

86 ms

util.js

util.js

90 ms

map.js

map.js

74 ms

overlay.js

overlay.js

143 ms

FBlores062s.jpg

FBlores062s.jpg

623 ms

FBlores008.jpg

FBlores008.jpg

643 ms

FBhires009s.jpg

FBhires009s.jpg

638 ms

FBhires013s.jpg

FBhires013s.jpg

664 ms

onion.js

onion.js

123 ms

search_impl.js

search_impl.js

123 ms

FBhires014s.jpg

FBhires014s.jpg

536 ms

FBhires025s.jpg

FBhires025s.jpg

538 ms

FBhires037s.jpg

FBhires037s.jpg

546 ms

FBhires038s.jpg

FBhires038s.jpg

580 ms

openhand_8_8.cur

openhand_8_8.cur

60 ms

FBhires039s.jpg

FBhires039s.jpg

509 ms

FBhires042s.jpg

FBhires042s.jpg

537 ms

FBhires044s.jpg

FBhires044s.jpg

540 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

127 ms

FBhires048s.jpg

FBhires048s.jpg

531 ms

FBhires052s.jpg

FBhires052s.jpg

535 ms

FBhires064s.jpg

FBhires064s.jpg

571 ms

FBlores016.jpg

FBlores016.jpg

545 ms

FBlores032s.jpg

FBlores032s.jpg

541 ms

FBlores035s.jpg

FBlores035s.jpg

532 ms

FBlores015.jpg

FBlores015.jpg

688 ms

FBlores005s.jpg

FBlores005s.jpg

547 ms

FBlores041s.jpg

FBlores041s.jpg

570 ms

FBlores016s.jpg

FBlores016s.jpg

646 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

33 ms

vt

vt

154 ms

vt

vt

135 ms

vt

vt

126 ms

vt

vt

132 ms

vt

vt

128 ms

vt

vt

131 ms

vt

vt

170 ms

vt

vt

168 ms

vt

vt

171 ms

vt

vt

214 ms

vt

vt

173 ms

vt

vt

172 ms

vt

vt

216 ms

vt

vt

216 ms

vt

vt

214 ms

vt

vt

220 ms

vt

vt

221 ms

vt

vt

230 ms

FBlores029s.jpg

FBlores029s.jpg

601 ms

FBlores017s.jpg

FBlores017s.jpg

599 ms

QuotaService.RecordEvent

QuotaService.RecordEvent

29 ms

FBlores033s.jpg

FBlores033s.jpg

578 ms

vt

vt

212 ms

vt

vt

229 ms

FBlores040s.jpg

FBlores040s.jpg

593 ms

FBlores012s.jpg

FBlores012s.jpg

588 ms

FBlores007s.jpg

FBlores007s.jpg

613 ms

FBlores020s.jpg

FBlores020s.jpg

580 ms

FBlores036s.jpg

FBlores036s.jpg

579 ms

FBlores001.jpg

FBlores001.jpg

577 ms

logo.png

logo.png

962 ms

ebike3.png

ebike3.png

754 ms

4.jpg

4.jpg

684 ms

10.jpg

10.jpg

548 ms

FBlores064.jpg

FBlores064.jpg

545 ms

FBlores007.jpg

FBlores007.jpg

542 ms

new.jpg

new.jpg

620 ms

old.jpg

old.jpg

599 ms

map.jpg

map.jpg

607 ms

controls.js

controls.js

5 ms

css

css

112 ms

css

css

136 ms

entity11.png

entity11.png

51 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

34 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

53 ms

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

66 ms

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

68 ms

Accessibility Review

francis-barnett.org accessibility score

78

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

francis-barnett.org 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

francis-barnett.org SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Francis-barnett.org 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 Francis-barnett.org 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

francis-barnett.org

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