Tools & Wizards About Us
a16sf.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

a16sf.com

A16 Pizza | Neighborhood Restaurant and Wine Spot in CA

Page Load Speed

1.2 sec in total

First Response

96 ms

Resources Loaded

973 ms

Page Rendered

118 ms

a16sf.com screenshot

About Website

Visit a16sf.com now to see the best up-to-date A16 Sf content for United States and also check out these interesting facts you probably never knew about a16sf.com

A16 is named after the autostrada which runs from Puglia (the home of burrata) to Naples, the heart of pizza country. We take our pizza craft seriously, traveling to the birthplace of pizza napoletana...

Visit a16sf.com

Key Findings

We analyzed A16sf.com page load time and found that the first response time was 96 ms and then it took 1.1 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

a16sf.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

a16sf.com

96 ms

www.a16sf.com

14 ms

a16pizza.com

126 ms

www.a16pizza.com

52 ms

bt

102 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original A16sf.com, 69% (29 requests) were made to Static.parastorage.com and 12% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (351 ms) relates to the external source Static.parastorage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (76%)

Content Size

2.6 MB

After Optimization

613.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of A16sf.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. 75% 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. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 19.9 kB

  • Original 26.3 kB
  • After minification 26.1 kB
  • After compression 6.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 19.9 kB or 76% of the original size.

JavaScript Optimization

-76%

Potential reduce by 1.9 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 598.4 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 1.9 MB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 44.1 kB

  • Original 52.5 kB
  • After minification 49.5 kB
  • After compression 8.5 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. A16sf.com needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (71%)

Requests Now

38

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

a16sf.com

a16sf.com

96 ms

www.a16sf.com

www.a16sf.com

14 ms

a16pizza.com

a16pizza.com

126 ms

www.a16pizza.com

www.a16pizza.com

52 ms

bt

bt

102 ms

require.min.js

require.min.js

57 ms

main-r.min.js

main-r.min.js

62 ms

viewer.css

viewer.css

61 ms

dynamicmodel

dynamicmodel

10 ms

d57b4c_a950c8ebb123476466410b6c554a46e6_120.json.z

d57b4c_a950c8ebb123476466410b6c554a46e6_120.json.z

118 ms

d57b4c_cafd281e906866c30548abe31314ca63_120.json.z

d57b4c_cafd281e906866c30548abe31314ca63_120.json.z

124 ms

ugc-viewer

ugc-viewer

112 ms

bt

bt

109 ms

skins.min.js

skins.min.js

116 ms

components.min.js

components.min.js

70 ms

utils.min.js

utils.min.js

32 ms

core.min.js

core.min.js

111 ms

react-with-addons.min.js

react-with-addons.min.js

108 ms

lodash.min.js

lodash.min.js

106 ms

TweenMax.min.js

TweenMax.min.js

106 ms

layout.min.js

layout.min.js

114 ms

tpa.min.js

tpa.min.js

351 ms

fonts.min.js

fonts.min.js

111 ms

animations.min.js

animations.min.js

113 ms

swfobject.min.js

swfobject.min.js

114 ms

mousetrap.min.js

mousetrap.min.js

348 ms

tweenEngine.min.js

tweenEngine.min.js

111 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

113 ms

react-dom.min.js

react-dom.min.js

112 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

344 ms

widgets.min.js

widgets.min.js

111 ms

experiment.js

experiment.js

112 ms

render.min.js

render.min.js

341 ms

wixappsCore.min.js

wixappsCore.min.js

347 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

341 ms

zepto.min.js

zepto.min.js

343 ms

color.min.js

color.min.js

343 ms

react-dom-server.min.js

react-dom-server.min.js

255 ms

bt

bt

160 ms

dc.js

dc.js

138 ms

bt

bt

94 ms

latin.css

latin.css

92 ms

Accessibility Review

a16sf.com accessibility score

96

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

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

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

a16sf.com best practices score

83

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

a16sf.com SEO score

98

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise A16sf.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 A16sf.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

a16sf.com

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