Tools & Wizards About Us
p3brampton.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

p3brampton.com

Brampton Print Store | Copy Centre | Full Service Printing | Print Three | Brampton | 24 Queen Street East

Page Load Speed

45.6 sec in total

First Response

16.7 sec

Resources Loaded

28.7 sec

Page Rendered

257 ms

p3brampton.com screenshot

About Website

Click here to check amazing P3 Brampton content. Otherwise, check out these important facts you probably never knew about p3brampton.com

Print Three Brampton is a full service printing store and copy centre. We provide digital printing services and graphic design services to the Brampton area.

Visit p3brampton.com

Key Findings

We analyzed P3brampton.com page load time and found that the first response time was 16.7 sec and then it took 28.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

p3brampton.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value26.7 s

0/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,460 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

p3brampton.com

16677 ms

mediaelementplayer-legacy.min.css

30 ms

wp-mediaelement.min.css

36 ms

woocommerce-layout.css

54 ms

woocommerce.css

91 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 29% of them (31 requests) were addressed to the original P3brampton.com, 38% (40 requests) were made to Vultr.racadtech.com and 11% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (16.7 sec) belongs to the original domain P3brampton.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (52%)

Content Size

2.0 MB

After Optimization

940.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of P3brampton.com main page is 2.0 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 801.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 111.6 kB

  • Original 137.2 kB
  • After minification 131.6 kB
  • After compression 25.6 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 111.6 kB or 81% of the original size.

Image Optimization

-30%

Potential reduce by 184.3 kB

  • Original 624.2 kB
  • After minification 439.9 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. Obviously, P3 Brampton needs image optimization as it can save up to 184.3 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-48%

Potential reduce by 386.8 kB

  • Original 801.4 kB
  • After minification 801.4 kB
  • After compression 414.6 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 386.8 kB or 48% of the original size.

CSS Optimization

-85%

Potential reduce by 347.5 kB

  • Original 408.2 kB
  • After minification 398.4 kB
  • After compression 60.6 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. P3brampton.com needs all CSS files to be minified and compressed as it can save up to 347.5 kB or 85% of the original size.

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 P3 Brampton. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

p3brampton.com

p3brampton.com

16677 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

30 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

36 ms

woocommerce-layout.css

woocommerce-layout.css

54 ms

woocommerce.css

woocommerce.css

91 ms

style.basic.css

style.basic.css

112 ms

style-simple-red.css

style-simple-red.css

119 ms

pum-site-styles-2.css

pum-site-styles-2.css

61 ms

frontend.min.css

frontend.min.css

84 ms

general.min.css

general.min.css

62 ms

eael-33.css

eael-33.css

116 ms

elementor-icons.min.css

elementor-icons.min.css

82 ms

swiper.min.css

swiper.min.css

82 ms

e-swiper.min.css

e-swiper.min.css

65 ms

post-3.css

post-3.css

92 ms

global.css

global.css

103 ms

wpforms-full.min.css

wpforms-full.min.css

52 ms

post-33.css

post-33.css

92 ms

theme.css

theme.css

53 ms

all.min.css

all.min.css

22 ms

css

css

84 ms

jquery.min.js

jquery.min.js

80 ms

jquery-migrate.min.js

jquery-migrate.min.js

58 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

63 ms

add-to-cart.min.js

add-to-cart.min.js

63 ms

js.cookie.min.js

js.cookie.min.js

63 ms

woocommerce.min.js

woocommerce.min.js

91 ms

s-202438.js

s-202438.js

62 ms

t.js

t.js

49 ms

css

css

58 ms

js

js

133 ms

wc-blocks.css

wc-blocks.css

88 ms

post-6529.css

post-6529.css

90 ms

widget-text-editor.min.css

widget-text-editor.min.css

90 ms

post-6540.css

post-6540.css

105 ms

post-6539.css

post-6539.css

106 ms

widget-image-box.min.css

widget-image-box.min.css

105 ms

post-6538.css

post-6538.css

106 ms

widget-heading.min.css

widget-heading.min.css

107 ms

widget-image.min.css

widget-image.min.css

129 ms

bootstrap.min.css

bootstrap.min.css

80 ms

widget-google_maps.min.css

widget-google_maps.min.css

115 ms

asl-prereq.js

asl-prereq.js

117 ms

asl-core.js

asl-core.js

119 ms

asl-results-vertical.js

asl-results-vertical.js

115 ms

asl-autocomplete.js

asl-autocomplete.js

116 ms

asl-load.js

asl-load.js

118 ms

asl-wrapper.js

asl-wrapper.js

118 ms

sourcebuster.min.js

sourcebuster.min.js

74 ms

order-attribution.min.js

order-attribution.min.js

73 ms

new-tab.js

new-tab.js

77 ms

core.min.js

core.min.js

92 ms

pum-site-scripts-2.js

pum-site-scripts-2.js

119 ms

general.min.js

general.min.js

116 ms

e-202438.js

e-202438.js

74 ms

webpack.runtime.min.js

webpack.runtime.min.js

114 ms

frontend-modules.min.js

frontend-modules.min.js

118 ms

frontend.min.js

frontend.min.js

117 ms

underscore.min.js

underscore.min.js

85 ms

wp-util.min.js

wp-util.min.js

90 ms

frontend.min.js

frontend.min.js

85 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

90 ms

single-product.min.js

single-product.min.js

90 ms

jquery.validate.min.js

jquery.validate.min.js

111 ms

mailcheck.min.js

mailcheck.min.js

92 ms

punycode.min.js

punycode.min.js

113 ms

wpforms.min.js

wpforms.min.js

114 ms

api.js

api.js

91 ms

css

css

34 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

49 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

9 ms

print3_logo.png

print3_logo.png

62 ms

submit-spin.svg

submit-spin.svg

46 ms

print3_logo_horizontal_reverse.png

print3_logo_horizontal_reverse.png

47 ms

Image1.png

Image1.png

49 ms

Image2.png

Image2.png

49 ms

Image3.png

Image3.png

50 ms

Icon.png

Icon.png

48 ms

Icon1.png

Icon1.png

47 ms

Icon2.png

Icon2.png

48 ms

Screenshot_26.png

Screenshot_26.png

122 ms

Awards-1024x160.png

Awards-1024x160.png

49 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

72 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

107 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

131 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

131 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

131 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

131 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

115 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

114 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

132 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

47 ms

fa-solid-900.ttf

fa-solid-900.ttf

69 ms

fa-regular-400.ttf

fa-regular-400.ttf

68 ms

fa-brands-400.ttf

fa-brands-400.ttf

69 ms

recaptcha__en.js

recaptcha__en.js

95 ms

embed

embed

392 ms

fallback

fallback

55 ms

fallback

fallback

54 ms

fallback

fallback

48 ms

fallback__ltr.css

fallback__ltr.css

4 ms

css

css

17 ms

logo_48.png

logo_48.png

10 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

3 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

5 ms

js

js

26 ms

Accessibility Review

p3brampton.com accessibility score

66

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Best Practices

p3brampton.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

p3brampton.com SEO score

92

Search Engine Optimization Advices

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

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

p3brampton.com

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