Tools & Wizards About Us
livingface.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

livingface.com

Corporate Event Photography Toronto | Corporate Headshot Photography

Page Load Speed

8 sec in total

First Response

2.8 sec

Resources Loaded

5.1 sec

Page Rendered

65 ms

livingface.com screenshot

About Website

Welcome to livingface.com homepage info - get ready to check Livingface best content for Canada right away, or after learning these important things about livingface.com

Skilled corporate event photographers Toronto | Quality & affordable corporate headshot photographer | Livingface Photography

Visit livingface.com

Key Findings

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

Performance Metrics

livingface.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value3,140 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

www.livingface.com

2813 ms

originTrials.41d7301a.bundle.min.js

37 ms

minified.js

43 ms

focus-within-polyfill.js

41 ms

polyfill.min.js

1103 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Livingface.com, 40% (25 requests) were made to Static.parastorage.com and 34% (21 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Livingface.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 748.7 kB (59%)

Content Size

1.3 MB

After Optimization

525.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Livingface.com main page is 1.3 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. 45% of websites need less resources to load. HTML takes 824.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 661.9 kB

  • Original 824.9 kB
  • After minification 823.2 kB
  • After compression 163.0 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 661.9 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 16.0 kB

  • Original 139.9 kB
  • After minification 123.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. Obviously, Livingface needs image optimization as it can save up to 16.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 70.8 kB

  • Original 309.3 kB
  • After minification 309.3 kB
  • After compression 238.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 70.8 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (24%)

Requests Now

50

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.livingface.com

www.livingface.com

2813 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

37 ms

minified.js

minified.js

43 ms

focus-within-polyfill.js

focus-within-polyfill.js

41 ms

polyfill.min.js

polyfill.min.js

1103 ms

thunderbolt-commons.01a1d4ab.bundle.min.js

thunderbolt-commons.01a1d4ab.bundle.min.js

17 ms

main.7ae9ac9b.bundle.min.js

main.7ae9ac9b.bundle.min.js

55 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

56 ms

lodash.min.js

lodash.min.js

56 ms

react.production.min.js

react.production.min.js

56 ms

react-dom.production.min.js

react-dom.production.min.js

56 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

58 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

58 ms

livingface_just-text-evensmaller.png

livingface_just-text-evensmaller.png

228 ms

5ce6cb_deb9002345434cf1b3d0c0ecf3e0df5a~mv2.jpg

5ce6cb_deb9002345434cf1b3d0c0ecf3e0df5a~mv2.jpg

465 ms

5ce6cb_bc8e39e3686e4d1fa0a93ca527640999~mv2.jpg

5ce6cb_bc8e39e3686e4d1fa0a93ca527640999~mv2.jpg

433 ms

5ce6cb_bc8e39e3686e4d1fa0a93ca527640999~mv2.jpg

5ce6cb_bc8e39e3686e4d1fa0a93ca527640999~mv2.jpg

433 ms

5ce6cb_45c445385166425788827973fa1003c5~mv2.jpg

5ce6cb_45c445385166425788827973fa1003c5~mv2.jpg

425 ms

5ce6cb_45c445385166425788827973fa1003c5~mv2.jpg

5ce6cb_45c445385166425788827973fa1003c5~mv2.jpg

434 ms

5ce6cb_a5c9d07231764b67a8b32ee02dce97c6~mv2.jpg

5ce6cb_a5c9d07231764b67a8b32ee02dce97c6~mv2.jpg

489 ms

5ce6cb_a5c9d07231764b67a8b32ee02dce97c6~mv2.jpg

5ce6cb_a5c9d07231764b67a8b32ee02dce97c6~mv2.jpg

523 ms

5ce6cb_13c3a955c0ad4020b1d97aae59d21071~mv2.jpg

5ce6cb_13c3a955c0ad4020b1d97aae59d21071~mv2.jpg

630 ms

5ce6cb_3a56799cccec4598b50aa1cbc49f4ccf~mv2_d_1803_1204_s_2.jpg

5ce6cb_3a56799cccec4598b50aa1cbc49f4ccf~mv2_d_1803_1204_s_2.jpg

644 ms

5ce6cb_5b6c943655104df09e1e8aa93b3704a9~mv2.jpg

5ce6cb_5b6c943655104df09e1e8aa93b3704a9~mv2.jpg

646 ms

Screen%20Shot%202019-04-09%20at%201_01_26%20PM.png

Screen%20Shot%202019-04-09%20at%201_01_26%20PM.png

729 ms

Screen%20Shot%202019-04-09%20at%201_02_03%20PM.png

Screen%20Shot%202019-04-09%20at%201_02_03%20PM.png

803 ms

Screen%20Shot%202019-04-09%20at%201_05_00%20PM.png

Screen%20Shot%202019-04-09%20at%201_05_00%20PM.png

722 ms

440px-Capital_One_logo_svg.png

440px-Capital_One_logo_svg.png

839 ms

Screen%20Shot%202019-04-09%20at%201_11_12%20PM.png

Screen%20Shot%202019-04-09%20at%201_11_12%20PM.png

848 ms

Untitled-1.jpg

Untitled-1.jpg

804 ms

IVEY-150.jpg

IVEY-150.jpg

887 ms

0.jpeg

0.jpeg

900 ms

0-1.jpeg

0-1.jpeg

1114 ms

5ce6cb_a20a2244a57e4340a75b913ba9e87028~mv2.jpg

5ce6cb_a20a2244a57e4340a75b913ba9e87028~mv2.jpg

999 ms

bundle.min.js

bundle.min.js

82 ms

I1Pn3gihk5vyP0Yw5GqKsQ.woff

I1Pn3gihk5vyP0Yw5GqKsQ.woff

39 ms

kU6VHbqMAZhaN_nXCmLQsQ.woff

kU6VHbqMAZhaN_nXCmLQsQ.woff

39 ms

AcvTq8Q0lyKKNxRlL28Rnz8E0i7KZn-EPnyo3HZu7kw.woff

AcvTq8Q0lyKKNxRlL28Rnz8E0i7KZn-EPnyo3HZu7kw.woff

38 ms

XNVd6tsqi9wmKNvnh5HNED8E0i7KZn-EPnyo3HZu7kw.woff

XNVd6tsqi9wmKNvnh5HNED8E0i7KZn-EPnyo3HZu7kw.woff

40 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

40 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

39 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

40 ms

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

40 ms

135 ms

131 ms

130 ms

126 ms

128 ms

130 ms

166 ms

162 ms

159 ms

159 ms

159 ms

163 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

19 ms

deprecation-style.v5.css

deprecation-style.v5.css

4 ms

right-arrow.svg

right-arrow.svg

8 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

6 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

5 ms

Accessibility Review

livingface.com accessibility score

86

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

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

Best Practices

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

livingface.com SEO score

93

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

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

livingface.com

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