Tools & Wizards About Us
timlittle.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

timlittle.com

Tim Little is an English Shoes designer based in London | Tim Little Shoes

Page Load Speed

16.8 sec in total

First Response

297 ms

Resources Loaded

16.4 sec

Page Rendered

103 ms

timlittle.com screenshot

About Website

Welcome to timlittle.com homepage info - get ready to check Tim Little best content for United Kingdom right away, or after learning these important things about timlittle.com

Tim Little is an English shoe designer and is the owner of Grenson. This is his personal collection of English and Italian made shoes, only available here and in his shop in Chelsea, London.

Visit timlittle.com

Key Findings

We analyzed Timlittle.com page load time and found that the first response time was 297 ms and then it took 16.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

timlittle.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

timlittle.com

297 ms

jquery-ui.js

32 ms

fabric.js

717 ms

all.js

392 ms

responsive-nav.css

160 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 91% of them (78 requests) were addressed to the original Timlittle.com, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (14.7 sec) belongs to the original domain Timlittle.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (79%)

Content Size

1.7 MB

After Optimization

355.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Timlittle.com main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.7 kB

  • Original 60.2 kB
  • After minification 54.3 kB
  • After compression 11.5 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 48.7 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 10 B

  • Original 8.1 kB
  • After minification 8.1 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. Tim Little images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 1.0 MB

  • Original 1.3 MB
  • After minification 835.9 kB
  • After compression 244.6 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 1.0 MB or 81% of the original size.

CSS Optimization

-76%

Potential reduce by 293.7 kB

  • Original 384.7 kB
  • After minification 336.5 kB
  • After compression 91.1 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. Timlittle.com needs all CSS files to be minified and compressed as it can save up to 293.7 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (90%)

Requests Now

83

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

timlittle.com

timlittle.com

297 ms

jquery-ui.js

jquery-ui.js

32 ms

fabric.js

fabric.js

717 ms

all.js

all.js

392 ms

responsive-nav.css

responsive-nav.css

160 ms

styles.css

styles.css

160 ms

responsive-nav.js

responsive-nav.js

161 ms

component.css

component.css

159 ms

modernizr.custom.js

modernizr.custom.js

238 ms

font-awesome.min.css

font-awesome.min.css

25 ms

default.css

default.css

237 ms

component.css

component.css

239 ms

owl.carousel.css

owl.carousel.css

240 ms

owl.theme.css

owl.theme.css

316 ms

font-awesome.min.css

font-awesome.min.css

392 ms

main.css

main.css

315 ms

smart-coupon.css

smart-coupon.css

316 ms

styles.css

styles.css

388 ms

sb-instagram.css

sb-instagram.css

467 ms

font-awesome.min.css

font-awesome.min.css

18 ms

modal-login.css

modal-login.css

391 ms

plugin-styles.css

plugin-styles.css

461 ms

video-js.css

video-js.css

544 ms

swatches-and-photos.css

swatches-and-photos.css

466 ms

woocommerce-layout.css

woocommerce-layout.css

468 ms

woocommerce.css

woocommerce.css

540 ms

colorbox.css

colorbox.css

543 ms

name-your-price.css

name-your-price.css

544 ms

chosen.css

chosen.css

551 ms

style.css

style.css

700 ms

dashicons.min.css

dashicons.min.css

794 ms

thickbox.css

thickbox.css

624 ms

admin_style.min.css

admin_style.min.css

625 ms

style.css

style.css

626 ms

jquery.js

jquery.js

947 ms

jquery-migrate.min.js

jquery-migrate.min.js

793 ms

popup.js

popup.js

792 ms

general.js

general.js

796 ms

modernizr.custom.js

modernizr.custom.js

795 ms

jquery.simplemodal.js

jquery.simplemodal.js

786 ms

jquery.form.min.js

jquery.form.min.js

654 ms

scripts.js

scripts.js

652 ms

sb-instagram.js

sb-instagram.js

738 ms

modal.js

modal.js

727 ms

modal-login.js

modal-login.js

650 ms

swatches-and-photos.js

swatches-and-photos.js

649 ms

add-to-cart.min.js

add-to-cart.min.js

650 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

727 ms

woocommerce.min.js

woocommerce.min.js

650 ms

jquery.cookie.min.js

jquery.cookie.min.js

650 ms

cart-fragments.min.js

cart-fragments.min.js

649 ms

toucheffects.js

toucheffects.js

588 ms

owl.carousel.js

owl.carousel.js

729 ms

plugin-main.js

plugin-main.js

652 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

649 ms

tim-little.js

tim-little.js

581 ms

thickbox.js

thickbox.js

577 ms

video.js

video.js

592 ms

vjs.youtube.js

vjs.youtube.js

653 ms

waypoints.min.js

waypoints.min.js

583 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

358 ms

css

css

62 ms

css

css

70 ms

reset.css

reset.css

338 ms

responsive.css

responsive.css

349 ms

analytics.js

analytics.js

38 ms

close.png

close.png

112 ms

loading.gif

loading.gif

116 ms

prev.png

prev.png

114 ms

next.png

next.png

116 ms

logo.png

logo.png

114 ms

logo-w.png

logo-w.png

114 ms

search.png

search.png

172 ms

footerlogo.png

footerlogo.png

170 ms

fb-fres.png

fb-fres.png

171 ms

in-fres.png

in-fres.png

170 ms

tw-fres.png

tw-fres.png

170 ms

dbclose-new.png

dbclose-new.png

169 ms

dbclose.png

dbclose.png

251 ms

bebas-webfont.woff

bebas-webfont.woff

228 ms

timlittle.com

timlittle.com

14700 ms

overlay.png

overlay.png

141 ms

loadingAnimation.gif

loadingAnimation.gif

144 ms

collect

collect

17 ms

collect

collect

59 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

81 ms

Accessibility Review

timlittle.com accessibility score

68

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

Image elements do not have [alt] attributes

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

timlittle.com 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

timlittle.com SEO score

86

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

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 Timlittle.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 Timlittle.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

timlittle.com

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