Tools & Wizards About Us
lewisfarley.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lewisfarley.com

Esports Filmmaker, Videographer, Director & Editor - LEWIS FARLEY - Work

Page Load Speed

4.5 sec in total

First Response

240 ms

Resources Loaded

2.8 sec

Page Rendered

1.5 sec

lewisfarley.com screenshot

About Website

Click here to check amazing LEWIS FARLEY content. Otherwise, check out these important facts you probably never knew about lewisfarley.com

Lewis Farley is a Blackpool based filmmaker, videographer, cinematographer specialising in esports, documentary, marketing and more.

Visit lewisfarley.com

Key Findings

We analyzed Lewisfarley.com page load time and found that the first response time was 240 ms and then it took 4.3 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

lewisfarley.com performance score

0

Network Requests Diagram

lewisfarley.com

240 ms

www.lewisfarley.com

227 ms

www.lewisfarley.com

427 ms

gdprscript.js

129 ms

sites.css

96 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 47% of them (27 requests) were addressed to the original Lewisfarley.com, 14% (8 requests) were made to Cdn2.editmysite.com and 14% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Lewisfarley.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 573.1 kB (30%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lewisfarley.com main page is 1.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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 30.2 kB

  • Original 38.5 kB
  • After minification 37.7 kB
  • After compression 8.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 30.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 6.6 kB

  • Original 1.1 MB
  • After minification 1.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. LEWIS FARLEY images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 216.1 kB

  • Original 405.2 kB
  • After minification 351.7 kB
  • After compression 189.1 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 216.1 kB or 53% of the original size.

CSS Optimization

-78%

Potential reduce by 320.3 kB

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

Requests Breakdown

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

Requests Now

45

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lewisfarley.com

lewisfarley.com

240 ms

www.lewisfarley.com

www.lewisfarley.com

227 ms

www.lewisfarley.com

www.lewisfarley.com

427 ms

gdprscript.js

gdprscript.js

129 ms

sites.css

sites.css

96 ms

fancybox.css

fancybox.css

95 ms

social-icons.css

social-icons.css

95 ms

main_style.css

main_style.css

239 ms

css

css

95 ms

css

css

105 ms

css

css

106 ms

jquery.min.js

jquery.min.js

76 ms

stl.js

stl.js

75 ms

main.js

main.js

80 ms

plugins.js

plugins.js

524 ms

jquery.pxuMenu.js

jquery.pxuMenu.js

619 ms

custom.js

custom.js

615 ms

mobile.js

mobile.js

640 ms

main-customer-accounts-site.js

main-customer-accounts-site.js

82 ms

zyAWOzehrWU

zyAWOzehrWU

429 ms

website-logo-2_1.png

website-logo-2_1.png

419 ms

g2_orig.png

g2_orig.png

692 ms

gereza_orig.jpg

gereza_orig.jpg

512 ms

dl_orig.jpg

dl_orig.jpg

689 ms

rise-thumbnail-for-1_orig.jpg

rise-thumbnail-for-1_orig.jpg

665 ms

the-poet-website.jpg

the-poet-website.jpg

665 ms

pesleague-thumb_1_orig.jpg

pesleague-thumb_1_orig.jpg

1035 ms

the-forgotten-thumbnail-for-site_orig.jpg

the-forgotten-thumbnail-for-site_orig.jpg

1034 ms

reel_orig.jpg

reel_orig.jpg

1035 ms

for-website_orig.jpg

for-website_orig.jpg

1036 ms

sceptic2_orig.jpg

sceptic2_orig.jpg

1237 ms

iceland-website-thumbnail_orig.jpg

iceland-website-thumbnail_orig.jpg

1238 ms

turning-pont-for-website_orig.jpg

turning-pont-for-website_orig.jpg

1239 ms

gezzaaa_1_orig.jpg

gezzaaa_1_orig.jpg

1282 ms

gbm_orig.jpg

gbm_orig.jpg

1284 ms

2_orig.jpg

2_orig.jpg

1436 ms

cod-for-web_orig.jpg

cod-for-web_orig.jpg

1339 ms

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGIVzZpabuWI.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffGjEGIVzZpabuWI.ttf

102 ms

NaPDcZTIAOhVxoMyOr9n_E7ffAzHGIVzZpabuWI.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffAzHGIVzZpabuWI.ttf

103 ms

NaPecZTIAOhVxoMyOr9n_E7fdM3mCKZRbrw.ttf

NaPecZTIAOhVxoMyOr9n_E7fdM3mCKZRbrw.ttf

125 ms

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGIVzZpabuWI.ttf

NaPDcZTIAOhVxoMyOr9n_E7ffHjDGIVzZpabuWI.ttf

127 ms

qkBWXvYC6trAT7zuC8m3xL5lmgzD.ttf

qkBWXvYC6trAT7zuC8m3xL5lmgzD.ttf

125 ms

qkBbXvYC6trAT7RbLtmU5rZP.ttf

qkBbXvYC6trAT7RbLtmU5rZP.ttf

127 ms

wsocial.woff

wsocial.woff

35 ms

www-player.css

www-player.css

61 ms

www-embed-player.js

www-embed-player.js

90 ms

base.js

base.js

274 ms

fetch-polyfill.js

fetch-polyfill.js

245 ms

ga.js

ga.js

267 ms

snowday262.js

snowday262.js

84 ms

805 ms

ad_status.js

ad_status.js

262 ms

embed.js

embed.js

57 ms

tp2

tp2

197 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

12 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

12 ms

id

id

47 ms

SEO Factors

lewisfarley.com SEO score

0

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

lewisfarley.com

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