Tools & Wizards About Us
hamishmackie.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

hamishmackie.com

Hamish Mackie Sculptor and his Bronze Wildlife Sculptures

Page Load Speed

2.9 sec in total

First Response

274 ms

Resources Loaded

1.8 sec

Page Rendered

791 ms

hamishmackie.com screenshot

About Website

Visit hamishmackie.com now to see the best up-to-date Hamish Mackie content and also check out these interesting facts you probably never knew about hamishmackie.com

Award-winning Oxfordshire sculptor Hamish Mackie is known worldwide for his bronze animal sculptures and wildlife and figurative works.

Visit hamishmackie.com

Key Findings

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

Performance Metrics

hamishmackie.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value5,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

hamishmackie.com

274 ms

hamishmackie.com

458 ms

02229.default.include.59f2c5.css

173 ms

02229.default.include.cfd850.js

249 ms

blocks.min.css

254 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 63% of them (36 requests) were addressed to the original Hamishmackie.com, 9% (5 requests) were made to Youtube.com and 9% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (881 ms) belongs to the original domain Hamishmackie.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.8 kB (8%)

Content Size

839.1 kB

After Optimization

769.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hamishmackie.com main page is 839.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 607.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 59.4 kB

  • Original 72.6 kB
  • After minification 59.9 kB
  • After compression 13.1 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. This page needs HTML code to be minified as it can gain 12.6 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 59.4 kB or 82% of the original size.

Image Optimization

-23%

Potential reduce by 916 B

  • Original 3.9 kB
  • After minification 3.0 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. Obviously, Hamish Mackie needs image optimization as it can save up to 916 B or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 7.3 kB

  • Original 607.3 kB
  • After minification 605.5 kB
  • After compression 600.0 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

-1%

Potential reduce by 2.1 kB

  • Original 155.3 kB
  • After minification 155.2 kB
  • After compression 153.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. Hamishmackie.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (76%)

Requests Now

49

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hamish Mackie. 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 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hamishmackie.com

hamishmackie.com

274 ms

hamishmackie.com

hamishmackie.com

458 ms

02229.default.include.59f2c5.css

02229.default.include.59f2c5.css

173 ms

02229.default.include.cfd850.js

02229.default.include.cfd850.js

249 ms

blocks.min.css

blocks.min.css

254 ms

app.min.css

app.min.css

348 ms

sbi-styles.min.css

sbi-styles.min.css

273 ms

style.min.css

style.min.css

356 ms

smartframe-custom.css

smartframe-custom.css

276 ms

dashicons.min.css

dashicons.min.css

413 ms

facets-styles.css

facets-styles.css

330 ms

style.css

style.css

360 ms

jquery.min.js

jquery.min.js

23 ms

svgs-inline-min.js

svgs-inline-min.js

360 ms

js

js

73 ms

smartframe.js

smartframe.js

25 ms

smartframe-public.js

smartframe-public.js

412 ms

smartframe-public.css

smartframe-public.css

449 ms

app.min.js

app.min.js

471 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

417 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

417 ms

wp-polyfill.min.js

wp-polyfill.min.js

538 ms

hooks.min.js

hooks.min.js

418 ms

i18n.min.js

i18n.min.js

437 ms

index.js

index.js

510 ms

index.js

index.js

509 ms

smartframe-custom.js

smartframe-custom.js

538 ms

scripts.js

scripts.js

576 ms

api.js

api.js

38 ms

index.js

index.js

745 ms

main.js

main.js

881 ms

02229.default.include-footer.2c5c76.js

02229.default.include-footer.2c5c76.js

879 ms

eso.m4v434v2.js

eso.m4v434v2.js

51 ms

css2

css2

34 ms

LER_SwkQk1k

LER_SwkQk1k

121 ms

HM-LOGO-1.svg

HM-LOGO-1.svg

530 ms

instagram.svg

instagram.svg

529 ms

pinterest.svg

pinterest.svg

532 ms

twitter.svg

twitter.svg

531 ms

facebook.svg

facebook.svg

731 ms

youtube.svg

youtube.svg

730 ms

HM-LOGO-footer.svg

HM-LOGO-footer.svg

728 ms

sbi-sprite.png

sbi-sprite.png

699 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4G1ilntA.ttf

22 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5ntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GCC5ntA.ttf

34 ms

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5ntA.ttf

pe1mMImSLYBIv1o4X1M8ce2xCx3yop4tQpF_MeTm0lfGWVpNn64CL7U8upHZIbMV51Q42ptCp5F5bxqqtQ1yiU4GMS5ntA.ttf

39 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

1 ms

www-player.css

www-player.css

46 ms

www-embed-player.js

www-embed-player.js

74 ms

base.js

base.js

114 ms

recaptcha__en.js

recaptcha__en.js

309 ms

ad_status.js

ad_status.js

344 ms

GkV5yKS0-OANEhjyXXxuzTYu8mVL2o5guieYvUh3n1c.js

GkV5yKS0-OANEhjyXXxuzTYu8mVL2o5guieYvUh3n1c.js

88 ms

embed.js

embed.js

44 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

195 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

195 ms

id

id

15 ms

Accessibility Review

hamishmackie.com accessibility score

90

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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 valid value for its [lang] attribute.

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

Links do not have a discernible name

Best Practices

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

Page has valid source maps

SEO Factors

hamishmackie.com SEO score

90

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

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

hamishmackie.com

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