Tools & Wizards About Us
scotslawblog.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

scotslawblog.com

Scots Law Blog | Scottish Law News | Welcome to Scots Law 2.0

Page Load Speed

8.7 sec in total

First Response

414 ms

Resources Loaded

8.1 sec

Page Rendered

189 ms

scotslawblog.com screenshot

About Website

Visit scotslawblog.com now to see the best up-to-date Scots Law Blog content and also check out these interesting facts you probably never knew about scotslawblog.com

Scots Law 2.0: Scots law blog posts, news & social media streams from a team of Scottish lawyers and law students. Become a columnist today.

Visit scotslawblog.com

Key Findings

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

Performance Metrics

scotslawblog.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.646

9/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

scotslawblog.com

414 ms

style.css

388 ms

layout.css

410 ms

custom.css

430 ms

style.min.css

456 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 29% of them (32 requests) were addressed to the original Scotslawblog.com, 27% (30 requests) were made to Pixel.wp.com and 18% (20 requests) were made to Cdn.api.twitter.com. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Fivefantasticlawyers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.5 kB (2%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Scotslawblog.com main page is 1.2 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. Images take 932.1 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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. This web page is already compressed.

Image Optimization

-2%

Potential reduce by 15.3 kB

  • Original 932.1 kB
  • After minification 916.8 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. Scots Law Blog images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.0 kB

  • Original 189.5 kB
  • After minification 189.5 kB
  • After compression 187.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 3.2 kB

  • Original 48.3 kB
  • After minification 48.2 kB
  • After compression 45.2 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. Scotslawblog.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 67 (87%)

Requests Now

77

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

scotslawblog.com

scotslawblog.com

414 ms

style.css

style.css

388 ms

layout.css

layout.css

410 ms

custom.css

custom.css

430 ms

style.min.css

style.min.css

456 ms

classic-themes.min.css

classic-themes.min.css

461 ms

styles.css

styles.css

462 ms

style.css

style.css

527 ms

genericons.css

genericons.css

630 ms

jetpack.css

jetpack.css

562 ms

style.css

style.css

576 ms

jquery.min.js

jquery.min.js

668 ms

jquery-migrate.min.js

jquery-migrate.min.js

578 ms

utils.min.js

utils.min.js

648 ms

ticker.js

ticker.js

94 ms

widgets.js

widgets.js

36 ms

feed.js

feed.js

110 ms

plusone.js

plusone.js

43 ms

hoverIntent.min.js

hoverIntent.min.js

707 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

707 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

707 ms

wp-polyfill.min.js

wp-polyfill.min.js

759 ms

hooks.min.js

hooks.min.js

785 ms

i18n.min.js

i18n.min.js

802 ms

common.min.js

common.min.js

811 ms

jquery.form.min.js

jquery.form.min.js

831 ms

scripts.js

scripts.js

832 ms

devicepx-jetpack.js

devicepx-jetpack.js

36 ms

gprofiles.js

gprofiles.js

36 ms

wpgroho.js

wpgroho.js

880 ms

sharing.js

sharing.js

895 ms

e-202406.js

e-202406.js

36 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

490 ms

Guest-legal-blogging-for-lawyers-guidelines.png

Guest-legal-blogging-for-lawyers-guidelines.png

53 ms

law-blog-award-winning-blog-uk.jpg

law-blog-award-winning-blog-uk.jpg

262 ms

icon-rss.gif

icon-rss.gif

288 ms

Scots-Law-Blog.png

Scots-Law-Blog.png

192 ms

dot-ddd.gif

dot-ddd.gif

291 ms

scots-law-legal-bloggers.jpg

scots-law-legal-bloggers.jpg

822 ms

loading.gif

loading.gif

323 ms

Genericons.svg

Genericons.svg

406 ms

8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=

8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=

12 ms

www.fivefantasticlawyers.com

www.fivefantasticlawyers.com

6407 ms

count.js

count.js

58 ms

all.js

all.js

19 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

all.js

all.js

20 ms

ga.js

ga.js

58 ms

g.gif

g.gif

64 ms

count.json

count.json

24 ms

count.json

count.json

23 ms

share

share

99 ms

count.json

count.json

23 ms

count.json

count.json

22 ms

share

share

196 ms

count.json

count.json

21 ms

count.json

count.json

27 ms

share

share

193 ms

count.json

count.json

27 ms

count.json

count.json

26 ms

share

share

201 ms

count.json

count.json

25 ms

count.json

count.json

25 ms

share

share

186 ms

count.json

count.json

24 ms

count.json

count.json

23 ms

share

share

145 ms

count.json

count.json

22 ms

count.json

count.json

22 ms

share

share

184 ms

count.json

count.json

21 ms

count.json

count.json

20 ms

share

share

213 ms

count.json

count.json

19 ms

count.json

count.json

19 ms

share

share

255 ms

count.json

count.json

19 ms

count.json

count.json

19 ms

share

share

232 ms

jetpack-count

jetpack-count

546 ms

g.gif

g.gif

44 ms

g.gif

g.gif

46 ms

g.gif

g.gif

46 ms

g.gif

g.gif

44 ms

g.gif

g.gif

45 ms

g.gif

g.gif

46 ms

g.gif

g.gif

46 ms

g.gif

g.gif

47 ms

g.gif

g.gif

46 ms

g.gif

g.gif

46 ms

g.gif

g.gif

47 ms

g.gif

g.gif

47 ms

g.gif

g.gif

46 ms

g.gif

g.gif

48 ms

g.gif

g.gif

48 ms

g.gif

g.gif

48 ms

g.gif

g.gif

48 ms

g.gif

g.gif

48 ms

g.gif

g.gif

48 ms

g.gif

g.gif

48 ms

g.gif

g.gif

49 ms

g.gif

g.gif

50 ms

g.gif

g.gif

49 ms

g.gif

g.gif

49 ms

g.gif

g.gif

50 ms

g.gif

g.gif

50 ms

g.gif

g.gif

51 ms

g.gif

g.gif

50 ms

g.gif

g.gif

50 ms

__utm.gif

__utm.gif

17 ms

Accessibility Review

scotslawblog.com accessibility score

76

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

button, link, and menuitem elements do not have accessible names.

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

scotslawblog.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

scotslawblog.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scotslawblog.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Scotslawblog.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

scotslawblog.com

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