Tools & Wizards About Us
pizzzar.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

pizzzar.com

PizzzAR™ Digital Platform | AR-enabled Interactive Advertising

Page Load Speed

1.3 sec in total

First Response

35 ms

Resources Loaded

846 ms

Page Rendered

409 ms

pizzzar.com screenshot

About Website

Visit pizzzar.com now to see the best up-to-date PizzzAR content for Canada and also check out these interesting facts you probably never knew about pizzzar.com

Experience the modern and cost effective AR-enabled Digital Advertising with PizzzAR Digital Platform.

Visit pizzzar.com

Key Findings

We analyzed Pizzzar.com page load time and found that the first response time was 35 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

pizzzar.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value10.5 s

8/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.634

9/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

pizzzar.com

35 ms

www.pizzzar.com

75 ms

cookie-consent.js

44 ms

lozad.min.js

20 ms

bundle.css

105 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 49% of them (17 requests) were addressed to the original Pizzzar.com, 17% (6 requests) were made to Fonts.gstatic.com and 14% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (519 ms) belongs to the original domain Pizzzar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 550.9 kB (21%)

Content Size

2.6 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pizzzar.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 53.5 kB

  • Original 67.0 kB
  • After minification 63.9 kB
  • After compression 13.5 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 53.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 128 B

  • Original 1.5 MB
  • After minification 1.5 MB

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. PizzzAR images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 149.7 kB

  • Original 614.0 kB
  • After minification 609.5 kB
  • After compression 464.3 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 149.7 kB or 24% of the original size.

CSS Optimization

-78%

Potential reduce by 347.5 kB

  • Original 444.8 kB
  • After minification 444.1 kB
  • After compression 97.3 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. Pizzzar.com needs all CSS files to be minified and compressed as it can save up to 347.5 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (60%)

Requests Now

25

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PizzzAR. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pizzzar.com

pizzzar.com

35 ms

www.pizzzar.com

www.pizzzar.com

75 ms

cookie-consent.js

cookie-consent.js

44 ms

lozad.min.js

lozad.min.js

20 ms

bundle.css

bundle.css

105 ms

style.css

style.css

77 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

99 ms

bundle.js

bundle.js

155 ms

js

js

70 ms

main.js

main.js

72 ms

tour360.js

tour360.js

96 ms

mc-validate.js

mc-validate.js

52 ms

J9mMzpOoaGw

J9mMzpOoaGw

238 ms

logo_light.png

logo_light.png

38 ms

logo_dark.png

logo_dark.png

40 ms

1x1.png

1x1.png

58 ms

css

css

34 ms

tree%20thank%20you.jpg

tree%20thank%20you.jpg

189 ms

2.jpg

2.jpg

519 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

171 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

205 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

207 ms

15.jpg

15.jpg

55 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

106 ms

et-line.woff

et-line.woff

52 ms

themify.woff

themify.woff

52 ms

www-player.css

www-player.css

15 ms

www-embed-player.js

www-embed-player.js

72 ms

base.js

base.js

101 ms

ad_status.js

ad_status.js

190 ms

fAKQRIhHJzkWPBJbxdRG8sE_4N5ZCu5h9VOYIQm4PUM.js

fAKQRIhHJzkWPBJbxdRG8sE_4N5ZCu5h9VOYIQm4PUM.js

115 ms

embed.js

embed.js

34 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

27 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

27 ms

id

id

32 ms

Accessibility Review

pizzzar.com accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pizzzar.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pizzzar.com SEO score

87

Search Engine Optimization Advices

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

pizzzar.com

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