Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

ianplant.com

Photography | Ian Plant Photography

Page Load Speed

991 ms in total

First Response

149 ms

Resources Loaded

704 ms

Page Rendered

138 ms

ianplant.com screenshot

About Website

Click here to check amazing Ian Plant content for United States. Otherwise, check out these important facts you probably never knew about ianplant.com

World-renowned photographer Ian Plant travels the globe looking for the most amazing places, people, wildlife, and moments to capture with his camera. Follow Ian on his photography adventures, and lea...

Visit ianplant.com

Key Findings

We analyzed Ianplant.com page load time and found that the first response time was 149 ms and then it took 842 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

ianplant.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

ianplant.com

149 ms

www.ianplant.com

165 ms

Ian-Plant-Photography.jpg

262 ms

Ian-Plant-Portfolio.jpg

260 ms

Ian-Plant-Estore.jpg

324 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original Ianplant.com, 15% (2 requests) were made to Google-analytics.com and 8% (1 request) were made to Classic.avantlink.com. The less responsive or slowest element that took the longest time to load (390 ms) belongs to the original domain Ianplant.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.6 kB (5%)

Content Size

265.4 kB

After Optimization

252.8 kB

In fact, the total size of Ianplant.com main page is 265.4 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. 15% of websites need less resources to load. Images take 222.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 6.3 kB

  • Original 9.0 kB
  • After minification 8.7 kB
  • After compression 2.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 6.3 kB or 70% of the original size.

Image Optimization

-3%

Potential reduce by 6.3 kB

  • Original 222.1 kB
  • After minification 215.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. Ian Plant images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 61 B

  • Original 34.3 kB
  • After minification 34.3 kB
  • After compression 34.2 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.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ian Plant. According to our analytics all requests are already optimized.

Accessibility Review

ianplant.com accessibility score

98

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.

Best Practices

ianplant.com best practices score

92

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

Page has valid source maps

SEO Factors

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

    EN

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ianplant.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 Ianplant.com main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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