Tools & Wizards About Us
livingface.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

livingface.com

Corporate Event Photography Toronto | Corporate Headshot Photography

Page Load Speed

1.4 sec in total

First Response

180 ms

Resources Loaded

758 ms

Page Rendered

504 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 180 ms and then it took 1.3 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

livingface.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value8,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

livingface.com

180 ms

www.livingface.com

309 ms

plusone.js

35 ms

cb=gapi.loaded_0

65 ms

ga.js

28 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 41% of them (13 requests) were addressed to the original Livingface.com, 25% (8 requests) were made to Apis.google.com and 16% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (309 ms) belongs to the original domain Livingface.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.7 kB (20%)

Content Size

309.8 kB

After Optimization

249.1 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-72%

Potential reduce by 28.4 kB

  • Original 39.3 kB
  • After minification 35.7 kB
  • After compression 10.9 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 28.4 kB or 72% of the original size.

Image Optimization

-11%

Potential reduce by 23.8 kB

  • Original 221.0 kB
  • After minification 197.2 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 23.8 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

-17%

Potential reduce by 8.6 kB

  • Original 49.6 kB
  • After minification 49.6 kB
  • After compression 41.0 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 8.6 kB or 17% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

18

  • AJAX
  • Images
  • JavaScript

The browser has sent 29 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

livingface.com

livingface.com

180 ms

www.livingface.com

www.livingface.com

309 ms

plusone.js

plusone.js

35 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

65 ms

ga.js

ga.js

28 ms

all.js

all.js

287 ms

splash_logo.jpg

splash_logo.jpg

150 ms

splash1.jpg

splash1.jpg

260 ms

splash2.jpg

splash2.jpg

127 ms

splash3.jpg

splash3.jpg

173 ms

facebook.png

facebook.png

127 ms

twitter.png

twitter.png

127 ms

youtube.png

youtube.png

203 ms

blogger.png

blogger.png

175 ms

googleplus.png

googleplus.png

175 ms

logo-google-local.png

logo-google-local.png

221 ms

__utm.gif

__utm.gif

53 ms

urchin.js

urchin.js

18 ms

counter.js

counter.js

17 ms

player.png

player.png

147 ms

t.php

t.php

100 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

20 ms

fastbutton

fastbutton

75 ms

__utm.gif

__utm.gif

23 ms

__utm.gif

__utm.gif

21 ms

postmessageRelay

postmessageRelay

44 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

16 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

17 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

35 ms

rpc:shindig_random.js

rpc:shindig_random.js

48 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

34 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 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

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

livingface.com SEO score

86

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Livingface.com main page’s claimed encoding is iso-8859-1. 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

livingface.com

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