Tools & Wizards About Us
brick.pizza screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

brick.pizza

Authentic Italian Pizzeria - 39 Market Place, Norwich | Brick Pizza

Page Load Speed

3.4 sec in total

First Response

343 ms

Resources Loaded

2.8 sec

Page Rendered

302 ms

brick.pizza screenshot

About Website

Welcome to brick.pizza homepage info - get ready to check Brick best content right away, or after learning these important things about brick.pizza

Welcome to Brick Pizza | 39 Market Place, Norwich | Download out Android and iOS app now for exclusive discounts and offers.

Visit brick.pizza

Key Findings

We analyzed Brick.pizza page load time and found that the first response time was 343 ms and then it took 3.1 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

brick.pizza performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

brick.pizza

343 ms

www.brick.pizza

670 ms

css

38 ms

jquery.min.js

28 ms

jquery-ui.min.js

47 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 93% of them (38 requests) were addressed to the original Brick.pizza, 5% (2 requests) were made to Ajax.googleapis.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (788 ms) belongs to the original domain Brick.pizza.

Page Optimization Overview & Recommendations

Page size can be reduced by 88.8 kB (15%)

Content Size

606.5 kB

After Optimization

517.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brick.pizza main page is 606.5 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. Javascripts take 272.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 34.2 kB

  • Original 41.9 kB
  • After minification 27.4 kB
  • After compression 7.7 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. This page needs HTML code to be minified as it can gain 14.6 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.2 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 4.7 kB

  • Original 166.0 kB
  • After minification 161.3 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. Brick images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 49.1 kB

  • Original 272.4 kB
  • After minification 271.2 kB
  • After compression 223.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 49.1 kB or 18% of the original size.

CSS Optimization

-1%

Potential reduce by 736 B

  • Original 126.1 kB
  • After minification 126.1 kB
  • After compression 125.4 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. Brick.pizza has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (74%)

Requests Now

38

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brick.pizza

brick.pizza

343 ms

www.brick.pizza

www.brick.pizza

670 ms

css

css

38 ms

jquery.min.js

jquery.min.js

28 ms

jquery-ui.min.js

jquery-ui.min.js

47 ms

order_chosen.js

order_chosen.js

80 ms

order_cookies.js

order_cookies.js

160 ms

order_easing.js

order_easing.js

240 ms

order_facebook.js

order_facebook.js

241 ms

order_fitvids.js

order_fitvids.js

239 ms

order_hammer.js

order_hammer.js

241 ms

order_imagesloaded.js

order_imagesloaded.js

242 ms

order_magnifik.js

order_magnifik.js

238 ms

order_map.js

order_map.js

317 ms

order_match_height.js

order_match_height.js

318 ms

order_mobileMenu.js

order_mobileMenu.js

319 ms

order_modals.js

order_modals.js

316 ms

order_overlay.js

order_overlay.js

319 ms

order_perfectScroll.js

order_perfectScroll.js

319 ms

order_responsive_tables.js

order_responsive_tables.js

394 ms

order_script.js

order_script.js

474 ms

order_select2.js

order_select2.js

475 ms

order_session.js

order_session.js

394 ms

order_slick.js

order_slick.js

396 ms

order_sticky.js

order_sticky.js

394 ms

order_sweetAlerts.js

order_sweetAlerts.js

551 ms

order_waypoints.js

order_waypoints.js

485 ms

order_zoom.js

order_zoom.js

484 ms

takeaway.js

takeaway.js

485 ms

jquery.form-validator.js

jquery.form-validator.js

555 ms

style.css

style.css

788 ms

order_checkout.js

order_checkout.js

553 ms

order_filter.js

order_filter.js

554 ms

fontAwesome.css

fontAwesome.css

80 ms

1561647056Largehomelogowhite.png

1561647056Largehomelogowhite.png

82 ms

156171092159541596_1876891105745936_696527391991791616_n.jpg

156171092159541596_1876891105745936_696527391991791616_n.jpg

156 ms

appstore.png

appstore.png

78 ms

googleplay.png

googleplay.png

79 ms

payment-cards.png

payment-cards.png

79 ms

hungrrr_logo.png

hungrrr_logo.png

80 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

232 ms

Accessibility Review

brick.pizza accessibility score

89

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

brick.pizza 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

Page has valid source maps

SEO Factors

brick.pizza 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 Brick.pizza 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 Brick.pizza 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

brick.pizza

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