Tools & Wizards About Us
gettyimages.ca screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 85

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

gettyimages.ca

Royalty-Free Stock Photos, Creative Images & Vectors | News, Fashion, and Entertainment imagery - Getty Images

Page Load Speed

1.6 sec in total

First Response

222 ms

Resources Loaded

1.3 sec

Page Rendered

117 ms

gettyimages.ca screenshot

About Website

Visit gettyimages.ca now to see the best up-to-date Getty Images content for Canada and also check out these interesting facts you probably never knew about gettyimages.ca

Discover Getty Images' unrivaled collection of royalty-free images to find the perfect stock photo, vector, or illustration that resonates with your customers.

Visit gettyimages.ca

Key Findings

We analyzed Gettyimages.ca page load time and found that the first response time was 222 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

gettyimages.ca performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

1/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value4,240 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.4 s

5/100

10%

Network Requests Diagram

www.gettyimages.ca

222 ms

unsupported

118 ms

getty-40cf1f9a3a7148b1d7538efb93320291.css

19 ms

application-244c1142e1b5a49835159bcf6b9be092.js

33 ms

GettyImages-logo-black-122x25-973c5dfd5144e113c2b99e40563b928a.png

31 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 35% of them (19 requests) were addressed to the original Gettyimages.ca, 19% (10 requests) were made to Sales.liveperson.net and 9% (5 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (227 ms) relates to the external source S2768.t.eloqua.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (73%)

Content Size

1.4 MB

After Optimization

385.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gettyimages.ca main page is 1.4 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 10.0 kB

  • Original 15.3 kB
  • After minification 15.3 kB
  • After compression 5.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. 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 10.0 kB or 65% of the original size.

Image Optimization

-16%

Potential reduce by 6.9 kB

  • Original 43.3 kB
  • After minification 36.4 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, Getty Images needs image optimization as it can save up to 6.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 907.3 kB

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

CSS Optimization

-83%

Potential reduce by 105.9 kB

  • Original 127.9 kB
  • After minification 127.2 kB
  • After compression 21.9 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. Gettyimages.ca needs all CSS files to be minified and compressed as it can save up to 105.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (62%)

Requests Now

47

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.gettyimages.ca

www.gettyimages.ca

222 ms

unsupported

unsupported

118 ms

getty-40cf1f9a3a7148b1d7538efb93320291.css

getty-40cf1f9a3a7148b1d7538efb93320291.css

19 ms

application-244c1142e1b5a49835159bcf6b9be092.js

application-244c1142e1b5a49835159bcf6b9be092.js

33 ms

GettyImages-logo-black-122x25-973c5dfd5144e113c2b99e40563b928a.png

GettyImages-logo-black-122x25-973c5dfd5144e113c2b99e40563b928a.png

31 ms

icon-chrome-85ae29bc4e2364360e24586980d1f45d.png

icon-chrome-85ae29bc4e2364360e24586980d1f45d.png

14 ms

icon-ff-c930ffa1ff083a9d23d1b9f522a6f3d3.png

icon-ff-c930ffa1ff083a9d23d1b9f522a6f3d3.png

31 ms

icon-safari-b264fdcd38538a9354b4222f7da56ff5.png

icon-safari-b264fdcd38538a9354b4222f7da56ff5.png

12 ms

icon-ie-11a5f78e495745b3eb60ebd2c52c0be1.png

icon-ie-11a5f78e495745b3eb60ebd2c52c0be1.png

31 ms

icon-warning.png

icon-warning.png

163 ms

header.js

header.js

116 ms

cookie_alert_bootstrapper.js

cookie_alert_bootstrapper.js

135 ms

site_catalyst.js

site_catalyst.js

9 ms

live_chat.js

live_chat.js

33 ms

Bootstrap.js

Bootstrap.js

30 ms

HelveticaNeueW01-55Roma.woff

HelveticaNeueW01-55Roma.woff

27 ms

HelveticaNeueW01-Thin.woff

HelveticaNeueW01-Thin.woff

28 ms

client_event

client_event

160 ms

mTag.js

mTag.js

55 ms

serverComponent.php

serverComponent.php

24 ms

stats

stats

172 ms

cookie_alert.css

cookie_alert.css

169 ms

s51621481101028

s51621481101028

56 ms

25 ms

81ded4115b3ed82468050ffc50fd4de5.js

81ded4115b3ed82468050ffc50fd4de5.js

44 ms

0c8ac87d32739a2ce171533416e343d1.js

0c8ac87d32739a2ce171533416e343d1.js

15 ms

de62c18dceecbe2010267a195d29585c.js

de62c18dceecbe2010267a195d29585c.js

16 ms

io.js

io.js

34 ms

lio.js

lio.js

52 ms

spx

spx

93 ms

elqCfg.min.js

elqCfg.min.js

21 ms

17 ms

33 ms

33 ms

irv3.js

irv3.js

28 ms

18 ms

conversion_async.js

conversion_async.js

24 ms

mediasource-A218913-dc0b-43b5-92cf-b5abffdabaa21-c-4202.js

mediasource-A218913-dc0b-43b5-92cf-b5abffdabaa21-c-4202.js

17 ms

svrGP

svrGP

101 ms

svrGP

svrGP

227 ms

14 ms

0cc652a55557cf28127f70bf821aeaaf

0cc652a55557cf28127f70bf821aeaaf

49 ms

8 ms

115390.02537536621

115390.02537536621

188 ms

11 ms

1*1.gif

1*1.gif

42 ms

12 ms

57 ms

st

st

80 ms

42 ms

svrGP.aspx

svrGP.aspx

40 ms

gs

gs

159 ms

xrefid.xgi

xrefid.xgi

7 ms

svrGP.aspx

svrGP.aspx

61 ms

Accessibility Review

gettyimages.ca accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

gettyimages.ca best practices score

85

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

Missing source maps for large first-party JavaScript

SEO Factors

gettyimages.ca SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 Gettyimages.ca 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 Gettyimages.ca 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

gettyimages.ca

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