Tools & Wizards About Us
fredperry.us screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fredperry.us

Fred Perry | Original Since 1952 | Fred Perry US

Page Load Speed

1.4 sec in total

First Response

175 ms

Resources Loaded

1000 ms

Page Rendered

245 ms

fredperry.us screenshot

About Website

Visit fredperry.us now to see the best up-to-date Fred Perry content for United States and also check out these interesting facts you probably never knew about fredperry.us

The brand founded by triple Wimbledon champion Fred Perry in 1952 and adopted by generations of British subcultures ever since. The Laurel Wreath is always worn as a badge of honour.

Visit fredperry.us

Key Findings

We analyzed Fredperry.us page load time and found that the first response time was 175 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

fredperry.us performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value4,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.9 s

0/100

10%

Network Requests Diagram

fredperry.us

175 ms

350 ms

8ffd7e5d72a441740253f43c4cc24de9.css

13 ms

80e7c8a288307d3eff240f06a7d05f9a.js

24 ms

css

93 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Fredperry.us, 35% (9 requests) were made to D1yk18ot3qjyqd.cloudfront.net and 15% (4 requests) were made to Fredperry.com. The less responsive or slowest element that took the longest time to load (446 ms) relates to the external source Track.adform.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (59%)

Content Size

1.8 MB

After Optimization

756.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fredperry.us main page is 1.8 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. 35% of websites need less resources to load. Javascripts take 877.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 29.9 kB

  • Original 42.2 kB
  • After minification 40.0 kB
  • After compression 12.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. 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 29.9 kB or 71% of the original size.

Image Optimization

-0%

Potential reduce by 1.1 kB

  • Original 493.1 kB
  • After minification 492.0 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. Fred Perry images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 674.2 kB

  • Original 877.1 kB
  • After minification 694.6 kB
  • After compression 202.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 674.2 kB or 77% of the original size.

CSS Optimization

-88%

Potential reduce by 373.4 kB

  • Original 422.9 kB
  • After minification 340.8 kB
  • After compression 49.5 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. Fredperry.us needs all CSS files to be minified and compressed as it can save up to 373.4 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (55%)

Requests Now

20

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fredperry.us

fredperry.us

175 ms

350 ms

8ffd7e5d72a441740253f43c4cc24de9.css

8ffd7e5d72a441740253f43c4cc24de9.css

13 ms

80e7c8a288307d3eff240f06a7d05f9a.js

80e7c8a288307d3eff240f06a7d05f9a.js

24 ms

css

css

93 ms

0dcf7c5154ca9877d85d2b249c1a9dd7.css

0dcf7c5154ca9877d85d2b249c1a9dd7.css

15 ms

fbds.js

fbds.js

36 ms

gtm.js

gtm.js

60 ms

vector-cache.js

vector-cache.js

5 ms

sheet-injector.js

sheet-injector.js

6 ms

mailcheck.min.js

mailcheck.min.js

84 ms

magentoMailcheck.js

magentoMailcheck.js

163 ms

init.js

init.js

22 ms

hammer.min.js

hammer.min.js

23 ms

icons.html

icons.html

191 ms

446 ms

ss16-dream-1-v1.jpg

ss16-dream-1-v1.jpg

60 ms

48 ms

analytics.js

analytics.js

7 ms

ec.js

ec.js

13 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

9 ms

texgyreheros-bold-webfont.woff

texgyreheros-bold-webfont.woff

7 ms

collect

collect

15 ms

collect

collect

37 ms

collect

collect

86 ms

collect

collect

72 ms

Accessibility Review

fredperry.us accessibility score

90

Accessibility Issues

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

fredperry.us 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fredperry.us SEO score

83

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

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

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 Fredperry.us 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 Fredperry.us 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

fredperry.us

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