Tools & Wizards About Us
edwintse.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

edwintse.com

Portraits — Edwin Tse Photography

Page Load Speed

786 ms in total

First Response

57 ms

Resources Loaded

593 ms

Page Rendered

136 ms

edwintse.com screenshot

About Website

Welcome to edwintse.com homepage info - get ready to check Edwin Tse best content right away, or after learning these important things about edwintse.com

photographer specializing in fashion, editorials, beauty, portrait work, music and celebrity, landscapes and documentaryphotographer, fashion, portrait, editorial, advertising, new york city, toronto,

Visit edwintse.com

Key Findings

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

Performance Metrics

edwintse.com performance score

0

Network Requests Diagram

www.edwintse.com

57 ms

SnJJFOlMHxOrFPeaSnz6KrUW9s9LQQ_bIQ-VhhakU0GfeqSJXnX1IyvhF2jtFRZLFQ4cF29UZcZ8FeJ3wD8KFQBRwebkFQMXe6MK2YgkdayTdAIldcNhjPG4fHvgIMMjgfMfqMYG_Fh0g6.js

63 ms

css2

67 ms

legacy.js

38 ms

modern.js

37 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Edwintse.com, 73% (61 requests) were made to Images.squarespace-cdn.com and 11% (9 requests) were made to Assets.squarespace.com. The less responsive or slowest element that took the longest time to load (170 ms) relates to the external source Images.squarespace-cdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.3 kB (9%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Edwintse.com main page is 1.6 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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 104.0 kB

  • Original 122.0 kB
  • After minification 111.1 kB
  • After compression 18.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. 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 104.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.9 kB

  • Original 400.0 kB
  • After minification 398.1 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. Edwin Tse images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 30.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 1.0 MB

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

Number of requests can be reduced by 13 (16%)

Requests Now

79

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.edwintse.com

www.edwintse.com

57 ms

SnJJFOlMHxOrFPeaSnz6KrUW9s9LQQ_bIQ-VhhakU0GfeqSJXnX1IyvhF2jtFRZLFQ4cF29UZcZ8FeJ3wD8KFQBRwebkFQMXe6MK2YgkdayTdAIldcNhjPG4fHvgIMMjgfMfqMYG_Fh0g6.js

SnJJFOlMHxOrFPeaSnz6KrUW9s9LQQ_bIQ-VhhakU0GfeqSJXnX1IyvhF2jtFRZLFQ4cF29UZcZ8FeJ3wD8KFQBRwebkFQMXe6MK2YgkdayTdAIldcNhjPG4fHvgIMMjgfMfqMYG_Fh0g6.js

63 ms

css2

css2

67 ms

legacy.js

legacy.js

38 ms

modern.js

modern.js

37 ms

extract-css-runtime-621e69d7b9c95772c873-min.en-US.js

extract-css-runtime-621e69d7b9c95772c873-min.en-US.js

37 ms

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

37 ms

cldr-resource-pack-e94539391642d3b99900-min.en-US.js

cldr-resource-pack-e94539391642d3b99900-min.en-US.js

37 ms

common-vendors-stable-3598b219a3c023c1915a-min.en-US.js

common-vendors-stable-3598b219a3c023c1915a-min.en-US.js

37 ms

common-vendors-6bd2e39357fb17aaed3a-min.en-US.js

common-vendors-6bd2e39357fb17aaed3a-min.en-US.js

47 ms

common-bc7ec1dac22b5edf1780-min.en-US.js

common-bc7ec1dac22b5edf1780-min.en-US.js

53 ms

performance-91cc73b28af6834e405d-min.en-US.js

performance-91cc73b28af6834e405d-min.en-US.js

40 ms

site.css

site.css

98 ms

js

js

96 ms

44 ms

logo.png

logo.png

170 ms

1.jpg

1.jpg

62 ms

2.jpg

2.jpg

61 ms

1.jpg

1.jpg

64 ms

2.jpg

2.jpg

62 ms

5.jpg

5.jpg

70 ms

1.jpg

1.jpg

71 ms

7.jpg

7.jpg

70 ms

2.jpg

2.jpg

71 ms

1.jpg

1.jpg

71 ms

3.jpg

3.jpg

71 ms

4.jpg

4.jpg

78 ms

5.jpg

5.jpg

78 ms

6.jpg

6.jpg

77 ms

13.jpg

13.jpg

76 ms

63.jpg

63.jpg

76 ms

10.jpg

10.jpg

76 ms

15.jpg

15.jpg

80 ms

17.jpg

17.jpg

82 ms

19.jpg

19.jpg

82 ms

20.jpg

20.jpg

78 ms

7.jpg

7.jpg

79 ms

8.jpg

8.jpg

82 ms

9.jpg

9.jpg

84 ms

10.jpg

10.jpg

84 ms

60.jpg

60.jpg

86 ms

26.jpg

26.jpg

86 ms

11.jpg

11.jpg

86 ms

12.jpg

12.jpg

85 ms

23.jpg

23.jpg

118 ms

13.jpg

13.jpg

87 ms

25.jpg

25.jpg

115 ms

15.jpg

15.jpg

114 ms

27.jpg

27.jpg

115 ms

14.jpg

14.jpg

114 ms

16.jpg

16.jpg

115 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

66 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

98 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

168 ms

d

d

65 ms

p.gif

p.gif

53 ms

js

js

87 ms

analytics.js

analytics.js

42 ms

17.jpg

17.jpg

71 ms

18.jpg

18.jpg

68 ms

19.jpg

19.jpg

62 ms

43.jpg

43.jpg

62 ms

21.jpg

21.jpg

66 ms

21.jpg

21.jpg

59 ms

23.jpg

23.jpg

61 ms

24.jpg

24.jpg

61 ms

30.jpg

30.jpg

59 ms

38.jpg

38.jpg

61 ms

39.jpg

39.jpg

60 ms

41.jpg

41.jpg

56 ms

42.jpg

42.jpg

113 ms

43.jpg

43.jpg

114 ms

44.jpg

44.jpg

115 ms

51.jpg

51.jpg

114 ms

26.jpg

26.jpg

115 ms

52.jpg

52.jpg

110 ms

27.jpg

27.jpg

112 ms

28.jpg

28.jpg

114 ms

29.jpg

29.jpg

112 ms

51.jpg

51.jpg

111 ms

52.jpg

52.jpg

112 ms

53.jpg

53.jpg

112 ms

68.jpg

68.jpg

110 ms

collect

collect

82 ms

SEO Factors

edwintse.com SEO score

0

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

edwintse.com

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