Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

Page Load Speed

1.3 sec in total

First Response

107 ms

Resources Loaded

1.1 sec

Page Rendered

90 ms

duncandavidson.com screenshot

About Website

Welcome to duncandavidson.com homepage info - get ready to check Duncandavidson best content for United States right away, or after learning these important things about duncandavidson.com

James Duncan Davidson is a photographer, software developer, and traveller based in Portland, Oregon. 

Visit duncandavidson.com

Key Findings

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

Performance Metrics

duncandavidson.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

94/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

duncandavidson.com

107 ms

z47nJhKFNJrZWTwiN0T9FEnLpWTwNcYaXuQpi2CP98bfezXgfFHN4UJLFRbh52jhWD93jD6Uw2ycZQsKwemKFDJDjhJkFcByFsTTZYm0jhB0ZeBh-AsDdht0jhNlOYiaikoqiAoRjAoqjWZTZYFzdKoRdhXCZYm0jhB0ZeBh-AsDdht0SaBujW48Sagyjh90jhNlOfG0ZYm0jhB0ZeBh-AsDdht0SaBujW48Sagyjh90jhNlJ6U3ScNt-AuyOAozicIK2hZcOWsTShIlihmKOWgkdkJHdWmDZAvlShB0SkG4fHXgIMMjgKMfH6qJlPSbMs6IJMJ7fbR1JyMgeMS6MKG4f4G1IMIj2KMfH6qJKfbbMs6sJMJ7fbRQ2UMfeMI6M6.js

60 ms

135 ms

duncandavidson.com

189 ms

common-6709d5c4f86c0097bed2-min.js

57 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 10% of them (2 requests) were addressed to the original Duncandavidson.com, 40% (8 requests) were made to Use.typekit.net and 20% (4 requests) were made to Static.squarespace.com. The less responsive or slowest element that took the longest time to load (246 ms) belongs to the original domain Duncandavidson.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.1 kB (69%)

Content Size

110.6 kB

After Optimization

34.5 kB

In fact, the total size of Duncandavidson.com main page is 110.6 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. 35% of websites need less resources to load. Javascripts take 56.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 41.6 kB

  • Original 53.9 kB
  • After minification 47.0 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 6.9 kB, which is 13% 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 41.6 kB or 77% of the original size.

JavaScript Optimization

-61%

Potential reduce by 34.6 kB

  • Original 56.7 kB
  • After minification 56.7 kB
  • After compression 22.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 34.6 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (38%)

Requests Now

13

After Optimization

8

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

Accessibility Review

duncandavidson.com accessibility score

93

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

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

SEO Factors

duncandavidson.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duncandavidson.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 Duncandavidson.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

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