Tools & Wizards About Us
pooleysword.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

pooleysword.com

Military and Presentation Sword Cutlers in Sussex - Pooley Sword

Page Load Speed

2.6 sec in total

First Response

247 ms

Resources Loaded

2.2 sec

Page Rendered

185 ms

pooleysword.com screenshot

About Website

Click here to check amazing Pooley Sword content. Otherwise, check out these important facts you probably never knew about pooleysword.com

Pooley Sword, Sussex, the leading Cutlers of military swords, dirks and lances to the British Armed Forces, Commonwealth & Overseas Defence Forces.

Visit pooleysword.com

Key Findings

We analyzed Pooleysword.com page load time and found that the first response time was 247 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pooleysword.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.157

74/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

pooleysword.com

247 ms

pooleysword.com

518 ms

style.css

126 ms

jquery.js

459 ms

jquery-validation.js

300 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 72% of them (21 requests) were addressed to the original Pooleysword.com, 7% (2 requests) were made to Player.vimeo.com and 7% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (925 ms) belongs to the original domain Pooleysword.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.6 kB (38%)

Content Size

257.4 kB

After Optimization

158.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pooleysword.com main page is 257.4 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. 45% of websites need less resources to load. Javascripts take 110.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 22.5 kB

  • Original 27.9 kB
  • After minification 24.1 kB
  • After compression 5.3 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 3.7 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 22.5 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 6.6 kB

  • Original 109.5 kB
  • After minification 102.9 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. Pooley Sword images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 61.6 kB

  • Original 110.0 kB
  • After minification 107.7 kB
  • After compression 48.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 61.6 kB or 56% of the original size.

CSS Optimization

-78%

Potential reduce by 7.9 kB

  • Original 10.1 kB
  • After minification 7.9 kB
  • After compression 2.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. Pooleysword.com needs all CSS files to be minified and compressed as it can save up to 7.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (20%)

Requests Now

25

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pooleysword.com

pooleysword.com

247 ms

pooleysword.com

pooleysword.com

518 ms

style.css

style.css

126 ms

jquery.js

jquery.js

459 ms

jquery-validation.js

jquery-validation.js

300 ms

jquery-validation-functions.js

jquery-validation-functions.js

314 ms

player.js

player.js

52 ms

platform.js

platform.js

42 ms

all.js

all.js

312 ms

css2

css2

31 ms

css2

css2

48 ms

pooley-sword-logo.jpg

pooley-sword-logo.jpg

256 ms

instagram.svg

instagram.svg

114 ms

facebook.svg

facebook.svg

108 ms

search.svg

search.svg

179 ms

menu.svg

menu.svg

115 ms

pooley-sword-home-mobile.webp

pooley-sword-home-mobile.webp

500 ms

pooley-sword-home1.webp

pooley-sword-home1.webp

442 ms

pooley-sword-home2.webp

pooley-sword-home2.webp

462 ms

pooley-sword-home3.webp

pooley-sword-home3.webp

518 ms

knot.svg

knot.svg

357 ms

pooley-sword-home4.webp

pooley-sword-home4.webp

557 ms

pooley-sword-home5.webp

pooley-sword-home5.webp

925 ms

pooley-sword-home6.webp

pooley-sword-home6.webp

906 ms

paypal-logo.svg

paypal-logo.svg

617 ms

905521790

905521790

323 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAw.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAw.ttf

61 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRUAw.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRUAw.ttf

69 ms

1786870252-a35c08b4f057a634b9ecaedc37ace5adfd048bf6c81b27a8fbb6901465724cd4-d

1786870252-a35c08b4f057a634b9ecaedc37ace5adfd048bf6c81b27a8fbb6901465724cd4-d

50 ms

Accessibility Review

pooleysword.com accessibility score

66

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

pooleysword.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pooleysword.com SEO score

76

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pooleysword.com 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 Pooleysword.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

pooleysword.com

Open Graph data is detected on the main page of Pooley Sword. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: