Tools & Wizards About Us
theparlor.us screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

theparlor.us

The Parlor Pizzeria - Authentic Italian Dining in Phoenix

Page Load Speed

3 sec in total

First Response

79 ms

Resources Loaded

1.6 sec

Page Rendered

1.3 sec

theparlor.us screenshot

About Website

Welcome to theparlor.us homepage info - get ready to check The Parlor best content for United States right away, or after learning these important things about theparlor.us

Experience the best of Italy in Phoenix with our wood-fired pizzas, handmade pastas, and craft cocktails made from the freshest local ingredients.

Visit theparlor.us

Key Findings

We analyzed Theparlor.us page load time and found that the first response time was 79 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

theparlor.us performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value18.4 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.201

62/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

theparlor.us

79 ms

theparlor.us

204 ms

styles.css

85 ms

style.css

151 ms

style.css

107 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 87% of them (87 requests) were addressed to the original Theparlor.us, 6% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (865 ms) belongs to the original domain Theparlor.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 707.3 kB (22%)

Content Size

3.2 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Theparlor.us main page is 3.2 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 534.6 kB

  • Original 594.6 kB
  • After minification 565.2 kB
  • After compression 60.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 534.6 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 101.5 kB

  • Original 1.8 MB
  • After minification 1.7 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. The Parlor images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 52.0 kB

  • Original 544.8 kB
  • After minification 543.9 kB
  • After compression 492.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

-9%

Potential reduce by 19.1 kB

  • Original 209.8 kB
  • After minification 209.8 kB
  • After compression 190.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. Theparlor.us has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 72 (80%)

Requests Now

90

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

theparlor.us

theparlor.us

79 ms

theparlor.us

theparlor.us

204 ms

styles.css

styles.css

85 ms

style.css

style.css

151 ms

style.css

style.css

107 ms

ut.core.fonts.min.css

ut.core.fonts.min.css

93 ms

ut.core.plugins.min.css

ut.core.plugins.min.css

99 ms

js_composer.min.css

js_composer.min.css

171 ms

ut.shortcode.min.css

ut.shortcode.min.css

115 ms

ut.vc.shortcodes.min.css

ut.vc.shortcodes.min.css

161 ms

ut.theme.min.css

ut.theme.min.css

129 ms

css

css

41 ms

jquery.min.js

jquery.min.js

201 ms

jquery-migrate.min.js

jquery-migrate.min.js

145 ms

modernizr.min.js

modernizr.min.js

216 ms

wpgmza_data.js

wpgmza_data.js

264 ms

ut-scriptlibrary.min.js

ut-scriptlibrary.min.js

269 ms

js

js

73 ms

css2

css2

55 ms

font-awesome.min.css

font-awesome.min.css

232 ms

fa-5to4.css

fa-5to4.css

231 ms

common.css

common.css

232 ms

remodal.css

remodal.css

233 ms

remodal-default-theme.css

remodal-default-theme.css

234 ms

jquery.dataTables.min.css

jquery.dataTables.min.css

253 ms

default.css

default.css

253 ms

owl.carousel.min.css

owl.carousel.min.css

254 ms

owl.theme.default.min.css

owl.theme.default.min.css

255 ms

carousel_sky.css

carousel_sky.css

255 ms

featherlight.min.css

featherlight.min.css

256 ms

dataTables.responsive.css

dataTables.responsive.css

255 ms

wpgmaps-admin.css

wpgmaps-admin.css

256 ms

wpgmza_style_pro.css

wpgmza_style_pro.css

257 ms

legacy-modern.css

legacy-modern.css

257 ms

formreset.min.css

formreset.min.css

258 ms

formsmain.min.css

formsmain.min.css

328 ms

readyclass.min.css

readyclass.min.css

329 ms

browsers.min.css

browsers.min.css

334 ms

ut.scplugin.min.js

ut.scplugin.min.js

336 ms

ut-init.min.js

ut-init.min.js

337 ms

js

js

79 ms

js_composer_front.min.js

js_composer_front.min.js

322 ms

dummy.js

dummy.js

294 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

283 ms

dataTables.responsive.js

dataTables.responsive.js

273 ms

jquery-cookie.js

jquery-cookie.js

273 ms

remodal.min.js

remodal.min.js

263 ms

pep.js

pep.js

250 ms

text.js

text.js

236 ms

pako_deflate.min.js

pako_deflate.min.js

222 ms

wp-google-maps-pro.min.js

wp-google-maps-pro.min.js

261 ms

owl.carousel.js

owl.carousel.js

257 ms

featherlight.min.js

featherlight.min.js

118 ms

polyline.js

polyline.js

191 ms

core.min.js

core.min.js

192 ms

mouse.min.js

mouse.min.js

191 ms

sortable.min.js

sortable.min.js

192 ms

CanvasLayerOptions.js

CanvasLayerOptions.js

191 ms

CanvasLayer.js

CanvasLayer.js

193 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

173 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

172 ms

wp-polyfill.min.js

wp-polyfill.min.js

175 ms

dom-ready.min.js

dom-ready.min.js

172 ms

hooks.min.js

hooks.min.js

172 ms

i18n.min.js

i18n.min.js

172 ms

a11y.min.js

a11y.min.js

171 ms

jquery.json.min.js

jquery.json.min.js

172 ms

gravityforms.min.js

gravityforms.min.js

189 ms

jquery.textareaCounter.plugin.min.js

jquery.textareaCounter.plugin.min.js

187 ms

utils.min.js

utils.min.js

189 ms

vendor-theme.min.js

vendor-theme.min.js

187 ms

scripts-theme.min.js

scripts-theme.min.js

118 ms

akismet-frontend.js

akismet-frontend.js

118 ms

ut.effects.min.js

ut.effects.min.js

128 ms

parlor-logo-176.png

parlor-logo-176.png

138 ms

PARLOR-Rotator-PizzaOven-Dk-1980x1200.jpg

PARLOR-Rotator-PizzaOven-Dk-1980x1200.jpg

790 ms

PARLOR-Rotator-Pasta-Dk-1980x1200.jpg

PARLOR-Rotator-Pasta-Dk-1980x1200.jpg

788 ms

PARLOR-Rotator-Octopus-Dk-1980x1200.jpg

PARLOR-Rotator-Octopus-Dk-1980x1200.jpg

789 ms

PARLOR-Rotator-WineCellar-Dk-1980x1200.jpg

PARLOR-Rotator-WineCellar-Dk-1980x1200.jpg

865 ms

PARLOR-Restaurant-12-e1445029906436.jpg

PARLOR-Restaurant-12-e1445029906436.jpg

787 ms

overlay-pattern.png

overlay-pattern.png

784 ms

PARLOR-Rotator-Dough3-1980x1200.jpg

PARLOR-Rotator-Dough3-1980x1200.jpg

863 ms

parlor-logo-219.png

parlor-logo-219.png

860 ms

directions_car.png

directions_car.png

860 ms

directions_walking.png

directions_walking.png

859 ms

directions_transit.png

directions_transit.png

858 ms

directions_bike.png

directions_bike.png

849 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

33 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

681 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

684 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

863 ms

XLYgIZbkc4JPUL5CVArUVL0nhnc.ttf

XLYgIZbkc4JPUL5CVArUVL0nhnc.ttf

686 ms

wlprgwHKFkZgtmSR3NB0oRJfajCOD9NV.ttf

wlprgwHKFkZgtmSR3NB0oRJfajCOD9NV.ttf

760 ms

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

686 ms

raleway-light-webfont.woff

raleway-light-webfont.woff

804 ms

PARLOR-Restaurant-18.jpg

PARLOR-Restaurant-18.jpg

795 ms

analytics.js

analytics.js

214 ms

collect

collect

41 ms

spotlight-poi3.png

spotlight-poi3.png

42 ms

js

js

39 ms

Accessibility Review

theparlor.us accessibility score

60

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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 IDs are not unique

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

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

theparlor.us best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

SEO Factors

theparlor.us SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Theparlor.us 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 Theparlor.us 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

theparlor.us

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