Tools & Wizards About Us
logsforlondon.co.uk screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

logsforlondon.co.uk

Logs for London - Top Quality Seasoned Hardwood Logs

Page Load Speed

16.5 sec in total

First Response

877 ms

Resources Loaded

15.4 sec

Page Rendered

166 ms

logsforlondon.co.uk screenshot

About Website

Visit logsforlondon.co.uk now to see the best up-to-date Logs For London content and also check out these interesting facts you probably never knew about logsforlondon.co.uk

Top Quality Seasoned Hardwood Logs London. We guarantee our firewood logs have been seasoned for 1 year and have low moisture content. Ready to burn now!

Visit logsforlondon.co.uk

Key Findings

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

logsforlondon.co.uk performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value25.0 s

0/100

25%

SI (Speed Index)

Value19.3 s

0/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.398

25/100

15%

TTI (Time to Interactive)

Value24.6 s

0/100

10%

Network Requests Diagram

logsforlondon.co.uk

877 ms

style.min.css

310 ms

jquery.selectBox.css

234 ms

font-awesome.css

314 ms

prettyPhoto.css

237 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 89% of them (58 requests) were addressed to the original Logsforlondon.co.uk, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Logsforlondon.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (66%)

Content Size

3.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Logsforlondon.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. 60% of websites need less resources to load. CSS take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 56.0 kB

  • Original 72.7 kB
  • After minification 70.9 kB
  • After compression 16.7 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 56.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 103 B

  • Original 614.0 kB
  • After minification 613.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. Logs For London images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 792.7 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 356.5 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 792.7 kB or 69% of the original size.

CSS Optimization

-89%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.5 MB
  • After compression 179.4 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. Logsforlondon.co.uk needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 89% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

logsforlondon.co.uk

logsforlondon.co.uk

877 ms

style.min.css

style.min.css

310 ms

jquery.selectBox.css

jquery.selectBox.css

234 ms

font-awesome.css

font-awesome.css

314 ms

prettyPhoto.css

prettyPhoto.css

237 ms

style.css

style.css

316 ms

styles.css

styles.css

235 ms

ml-responsive-table.css

ml-responsive-table.css

314 ms

extendify-utilities.css

extendify-utilities.css

470 ms

topbar_style.css

topbar_style.css

315 ms

utility-minimum.css

utility-minimum.css

389 ms

js_composer.min.css

js_composer.min.css

776 ms

et-fonts.css

et-fonts.css

391 ms

style.css

style.css

703 ms

responsive.css

responsive.css

548 ms

large-resolution.css

large-resolution.css

468 ms

css

css

30 ms

jquery.min.js

jquery.min.js

551 ms

jquery-migrate.min.js

jquery-migrate.min.js

478 ms

ml.responsive.table.min.js

ml.responsive.table.min.js

478 ms

wpgmza_data.js

wpgmza_data.js

555 ms

tpbr_front.min.js

tpbr_front.min.js

556 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

556 ms

add-to-cart.min.js

add-to-cart.min.js

644 ms

js.cookie.min.js

js.cookie.min.js

644 ms

woocommerce.min.js

woocommerce.min.js

645 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

645 ms

head.js

head.js

739 ms

underscore.min.js

underscore.min.js

742 ms

wp-util.min.js

wp-util.min.js

744 ms

rs6.css

rs6.css

755 ms

comment-reply.min.js

comment-reply.min.js

755 ms

jquery.selectBox.min.js

jquery.selectBox.min.js

787 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

801 ms

jquery.yith-wcwl.min.js

jquery.yith-wcwl.min.js

788 ms

index.js

index.js

806 ms

index.js

index.js

806 ms

rbtools.min.js

rbtools.min.js

965 ms

rs6.min.js

rs6.min.js

711 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

707 ms

plugins.min.js

plugins.min.js

713 ms

waypoints.min.js

waypoints.min.js

649 ms

etheme.min.js

etheme.min.js

648 ms

js_composer_front.min.js

js_composer_front.min.js

705 ms

analytics.js

analytics.js

40 ms

logsforlondonlogo2.jpg

logsforlondonlogo2.jpg

197 ms

icon-zoom.png

icon-zoom.png

212 ms

black_cross.png

black_cross.png

213 ms

dummy.png

dummy.png

213 ms

volume_banner.jpg

volume_banner.jpg

237 ms

source_banner.jpg

source_banner.jpg

311 ms

wood_banner.jpg

wood_banner.jpg

315 ms

order_banner.jpg

order_banner.jpg

314 ms

logbag-150x150.png

logbag-150x150.png

239 ms

BRF-Logo.jpg

BRF-Logo.jpg

1082 ms

cert-logos-1.jpg

cert-logos-1.jpg

394 ms

OpenSans-Regular.ttf

OpenSans-Regular.ttf

425 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

38 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

42 ms

OpenSans-Light.ttf

OpenSans-Light.ttf

269 ms

OpenSans-Bold.ttf

OpenSans-Bold.ttf

275 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

29 ms

arrows.woff

arrows.woff

261 ms

collect

collect

21 ms

js

js

72 ms

Accessibility Review

logsforlondon.co.uk accessibility score

61

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

logsforlondon.co.uk best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

logsforlondon.co.uk SEO score

83

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

logsforlondon.co.uk

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