Tools & Wizards About Us
footway.co.uk screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

footway.co.uk

Shoes online at FOOTWAY.com - 30,000 shoes from 650 brands | Footway

Page Load Speed

4.8 sec in total

First Response

213 ms

Resources Loaded

2 sec

Page Rendered

2.6 sec

footway.co.uk screenshot

About Website

Click here to check amazing FOOTWAY content for United Kingdom. Otherwise, check out these important facts you probably never knew about footway.co.uk

Buy shoes online at FOOTWAY.com. Womens shoes, kids shoes and mens shoes for all occasions. ✔️ 365 days free returns ✔️ Fast delivery

Visit footway.co.uk

Key Findings

We analyzed Footway.co.uk page load time and found that the first response time was 213 ms and then it took 4.6 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

footway.co.uk performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

footway.co.uk

213 ms

gb

1314 ms

polyfills-5cd94c89d3acac5f.js

63 ms

optimize.js

129 ms

8040.c154d3d9849ec3b2.js

63 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Footway.co.uk, 58% (33 requests) were made to Web-assets.footway.com and 30% (17 requests) were made to Images.footway.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Footway.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 330.6 kB (10%)

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images

In fact, the total size of Footway.co.uk main page is 3.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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 330.2 kB

  • Original 400.6 kB
  • After minification 400.6 kB
  • After compression 70.4 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 330.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 355 B

  • Original 3.0 MB
  • After minification 3.0 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. FOOTWAY images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 33 (65%)

Requests Now

51

After Optimization

18

  • Images
  • JavaScript

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

Network Requests Diagram

footway.co.uk

footway.co.uk

213 ms

gb

gb

1314 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

63 ms

optimize.js

optimize.js

129 ms

8040.c154d3d9849ec3b2.js

8040.c154d3d9849ec3b2.js

63 ms

985.39c60299c8076d2c.js

985.39c60299c8076d2c.js

63 ms

7902.8c4f0e4126204574.js

7902.8c4f0e4126204574.js

65 ms

1148.2a61af80f3a90f89.js

1148.2a61af80f3a90f89.js

116 ms

273-e81b5c25bc02d20c.js

273-e81b5c25bc02d20c.js

63 ms

2464-04bfda4d3fb3dc80.js

2464-04bfda4d3fb3dc80.js

65 ms

5696-4b5c6ff8f833a1e0.js

5696-4b5c6ff8f833a1e0.js

116 ms

8333.8f56423627d97056.js

8333.8f56423627d97056.js

112 ms

2922-9b183dee904e6d36.js

2922-9b183dee904e6d36.js

115 ms

8566-3be39cf9e1dd8a83.js

8566-3be39cf9e1dd8a83.js

117 ms

1880.d85def109087022f.js

1880.d85def109087022f.js

117 ms

7676.1238ed8f7d4c364f.js

7676.1238ed8f7d4c364f.js

117 ms

3153-1849a31663e7d36b.js

3153-1849a31663e7d36b.js

117 ms

2430.5559050b58c3ce75.js

2430.5559050b58c3ce75.js

118 ms

4803.9542340e46ac376f.js

4803.9542340e46ac376f.js

117 ms

webpack-021d9d583ece481f.js

webpack-021d9d583ece481f.js

118 ms

framework-568b840ecff66744.js

framework-568b840ecff66744.js

571 ms

main-5d0af15a48abbd86.js

main-5d0af15a48abbd86.js

118 ms

_app-b6614b50ea4d9522.js

_app-b6614b50ea4d9522.js

121 ms

6659-21ea79fba50dbc9a.js

6659-21ea79fba50dbc9a.js

118 ms

5331-dd4296780c6e3d44.js

5331-dd4296780c6e3d44.js

119 ms

4637-580d0032360b7bd6.js

4637-580d0032360b7bd6.js

118 ms

8584-01b719d30d459d1b.js

8584-01b719d30d459d1b.js

117 ms

5426-a748dd5caca89d7f.js

5426-a748dd5caca89d7f.js

119 ms

5337-988a6dc311b69fc1.js

5337-988a6dc311b69fc1.js

119 ms

2450-26488a616790b7aa.js

2450-26488a616790b7aa.js

121 ms

2943-3c8a9ba9786b0732.js

2943-3c8a9ba9786b0732.js

120 ms

3272-a9dd0b8deeea1d0d.js

3272-a9dd0b8deeea1d0d.js

120 ms

index-c084668850f7e77d.js

index-c084668850f7e77d.js

121 ms

_buildManifest.js

_buildManifest.js

122 ms

_ssgManifest.js

_ssgManifest.js

121 ms

_middlewareManifest.js

_middlewareManifest.js

121 ms

1724857788601_btschool_small3.jpg

1724857788601_btschool_small3.jpg

110 ms

1724857406878_tretornhalf.jpg

1724857406878_tretornhalf.jpg

102 ms

1721660301216_dep_lila.png

1721660301216_dep_lila.png

101 ms

1721660323344_dep_lila.png

1721660323344_dep_lila.png

102 ms

1721660350012_dep_lila.png

1721660350012_dep_lila.png

102 ms

1721660373942_dep_lila.png

1721660373942_dep_lila.png

103 ms

1677840677680_sneakers.jpg

1677840677680_sneakers.jpg

104 ms

1677840439727_sport.jpg

1677840439727_sport.jpg

108 ms

1666871336307_sandals.jpg

1666871336307_sandals.jpg

109 ms

1681819781972_slip-on.jpg

1681819781972_slip-on.jpg

109 ms

1662994485950_boots.jpg

1662994485950_boots.jpg

105 ms

1677840195571_boots.jpg

1677840195571_boots.jpg

107 ms

1666871372053_rubberboots.jpg

1666871372053_rubberboots.jpg

109 ms

1681819881367_slippers.jpg

1681819881367_slippers.jpg

109 ms

1716283292708_ecco%20h2.jpg

1716283292708_ecco%20h2.jpg

112 ms

1713439961421_merrell_front.jpg

1713439961421_merrell_front.jpg

113 ms

1716295461536_axelda_h2.jpg

1716295461536_axelda_h2.jpg

111 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

68 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

76 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

83 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

84 ms

Accessibility Review

footway.co.uk accessibility score

73

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

footway.co.uk 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

Missing source maps for large first-party JavaScript

SEO Factors

footway.co.uk SEO score

91

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

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 Footway.co.uk 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 Footway.co.uk 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

footway.co.uk

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