Tools & Wizards About Us
puritanslice.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

puritanslice.com

Puritan Restaurant - Boston, MA

Page Load Speed

1.3 sec in total

First Response

11 ms

Resources Loaded

580 ms

Page Rendered

701 ms

puritanslice.com screenshot

About Website

Welcome to puritanslice.com homepage info - get ready to check Puritan Slice best content right away, or after learning these important things about puritanslice.com

We are located at 735 William T Morrissey Blvd, Boston, MA 02122.

Visit puritanslice.com

Key Findings

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

puritanslice.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

puritanslice.com

11 ms

puritanslice.com

187 ms

styles.css

6 ms

main.css

37 ms

wp-sentry-browser.min.js

32 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 70% of them (19 requests) were addressed to the original Puritanslice.com, 11% (3 requests) were made to Wp1.foodtecsolutions.com and 7% (2 requests) were made to Api.tiles.mapbox.com. The less responsive or slowest element that took the longest time to load (188 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.2 kB (1%)

Content Size

5.1 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Puritanslice.com main page is 5.1 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. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 37.0 kB

  • Original 47.2 kB
  • After minification 47.2 kB
  • After compression 10.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 37.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 34.9 kB

  • Original 4.7 MB
  • After minification 4.6 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. Puritan Slice images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 333.1 kB
  • After minification 333.1 kB
  • After compression 331.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 125 B

  • Original 49.9 kB
  • After minification 49.9 kB
  • After compression 49.7 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. Puritanslice.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

puritanslice.com

puritanslice.com

11 ms

puritanslice.com

puritanslice.com

187 ms

styles.css

styles.css

6 ms

main.css

main.css

37 ms

wp-sentry-browser.min.js

wp-sentry-browser.min.js

32 ms

jquery.min.js

jquery.min.js

33 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

76 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

77 ms

public.js

public.js

83 ms

main.js

main.js

21 ms

mapbox-gl.css

mapbox-gl.css

78 ms

frontend.js

frontend.js

75 ms

mapbox-gl.js

mapbox-gl.js

139 ms

api.js

api.js

188 ms

gtm.js

gtm.js

187 ms

background.jpg

background.jpg

91 ms

C1D857FA-A90A-46BF-881B-FA0CE51E862C-scaled.jpg

C1D857FA-A90A-46BF-881B-FA0CE51E862C-scaled.jpg

163 ms

IMG_7251-scaled.jpg

IMG_7251-scaled.jpg

164 ms

IMG_7270-scaled.jpg

IMG_7270-scaled.jpg

164 ms

IMG_7358-scaled.jpg

IMG_7358-scaled.jpg

162 ms

IMG_7366-scaled.jpg

IMG_7366-scaled.jpg

169 ms

IMG_7402-scaled.jpg

IMG_7402-scaled.jpg

165 ms

Image.gif

Image.gif

166 ms

logo.png

logo.png

165 ms

recaptcha__en.js

recaptcha__en.js

117 ms

fa-solid-900.woff

fa-solid-900.woff

25 ms

fa-regular-400.woff

fa-regular-400.woff

25 ms

Accessibility Review

puritanslice.com accessibility score

89

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

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.

Best Practices

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

puritanslice.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

puritanslice.com

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