Tools & Wizards About Us
pcnametag.ca screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 66

    SEO

    Google-friendlier than
    26% of websites

pcnametag.ca

Name Tags, Event Badges, Lanyards, Badge Ribbons and more | pc/nametag Canada

Page Load Speed

4.5 sec in total

First Response

37 ms

Resources Loaded

4.2 sec

Page Rendered

242 ms

pcnametag.ca screenshot

About Website

Welcome to pcnametag.ca homepage info - get ready to check Pc Nametag best content for Canada right away, or after learning these important things about pcnametag.ca

pc/nametag makes memorable and meaningful connections that create extraordinary events for ever lasting impressions

Visit pcnametag.ca

Key Findings

We analyzed Pcnametag.ca page load time and found that the first response time was 37 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

pcnametag.ca performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value3,380 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.242

51/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

pcnametag.ca

37 ms

649 ms

calendar.css

66 ms

styles-m.css

39 ms

bootstrap.min.css

68 ms

Our browser made a total of 196 requests to load all elements on the main page. We found that 62% of them (122 requests) were addressed to the original Pcnametag.ca, 29% (56 requests) were made to Assets.pcnametag.ca and 3% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Assets.pcnametag.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 646.8 kB (11%)

Content Size

5.8 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pcnametag.ca main page is 5.8 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 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 170.0 kB

  • Original 210.9 kB
  • After minification 188.1 kB
  • After compression 40.9 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 22.8 kB, which is 11% 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 170.0 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 233.0 kB

  • Original 4.9 MB
  • After minification 4.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. Pc Nametag images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 230.4 kB

  • Original 546.6 kB
  • After minification 543.1 kB
  • After compression 316.2 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 230.4 kB or 42% of the original size.

CSS Optimization

-10%

Potential reduce by 13.4 kB

  • Original 130.1 kB
  • After minification 130.1 kB
  • After compression 116.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. Pcnametag.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 122 (67%)

Requests Now

181

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pcnametag.ca

pcnametag.ca

37 ms

649 ms

calendar.css

calendar.css

66 ms

styles-m.css

styles-m.css

39 ms

bootstrap.min.css

bootstrap.min.css

68 ms

fontawesome-all.min.css

fontawesome-all.min.css

27 ms

main-style.css

main-style.css

30 ms

owl.carousel.min.css

owl.carousel.min.css

77 ms

style.css

style.css

78 ms

style.css

style.css

84 ms

grid-mageplaza.css

grid-mageplaza.css

83 ms

styles-l.css

styles-l.css

85 ms

require.js

require.js

83 ms

mixins.js

mixins.js

82 ms

requirejs-config.js

requirejs-config.js

83 ms

email-decode.min.js

email-decode.min.js

94 ms

_dmpt.js

_dmpt.js

94 ms

pa-60f873c10678540011000056.js

pa-60f873c10678540011000056.js

411 ms

CobrowseJS.ashx

CobrowseJS.ashx

59 ms

zok0pfj.css

zok0pfj.css

126 ms

GlanceCobrowseLoader_6.26.0M.js

GlanceCobrowseLoader_6.26.0M.js

40 ms

print.css

print.css

24 ms

p.css

p.css

28 ms

analytics.js

analytics.js

150 ms

gtm.js

gtm.js

219 ms

649 ms

logo.svg

logo.svg

144 ms

format=WEB

format=WEB

726 ms

712 ms

53878418359

53878418359

705 ms

702 ms

707 ms

891 ms

920 ms

1006 ms

921 ms

1014 ms

1156 ms

1098 ms

1138 ms

1161 ms

1258 ms

1245 ms

1350 ms

1370 ms

1368 ms

1395 ms

1474 ms

1462 ms

1713 ms

1615 ms

1836 ms

1641 ms

1669 ms

2145 ms

1832 ms

1875 ms

2030 ms

1932 ms

2042 ms

2042 ms

2320 ms

jquery.mobile.custom.js

jquery.mobile.custom.js

179 ms

dataPost.js

dataPost.js

179 ms

bootstrap.js

bootstrap.js

178 ms

translate-inline.js

translate-inline.js

176 ms

responsive.js

responsive.js

176 ms

theme.js

theme.js

175 ms

main-script.js

main-script.js

236 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

235 ms

js.cookie.js

js.cookie.js

236 ms

translate.js

translate.js

235 ms

opensans-400.woff

opensans-400.woff

302 ms

opensans-300.woff

opensans-300.woff

302 ms

opensans-600.woff

opensans-600.woff

355 ms

opensans-700.woff

opensans-700.woff

355 ms

jquery.js

jquery.js

174 ms

jquery.cookie.js

jquery.cookie.js

175 ms

d

d

77 ms

d

d

147 ms

d

d

147 ms

d

d

134 ms

d

d

117 ms

Luma-Icons.woff

Luma-Icons.woff

269 ms

fa-solid-900.woff

fa-solid-900.woff

287 ms

fa-regular-400.woff

fa-regular-400.woff

253 ms

collect

collect

81 ms

_dmptv4.js

_dmptv4.js

108 ms

tabs.js

tabs.js

124 ms

domReady.js

domReady.js

177 ms

smart-keyboard-handler.js

smart-keyboard-handler.js

176 ms

mage.js

mage.js

176 ms

ie-class-fixer.js

ie-class-fixer.js

177 ms

template.js

template.js

176 ms

confirm.js

confirm.js

176 ms

main.js

main.js

204 ms

bootstrap.js

bootstrap.js

207 ms

matchMedia.js

matchMedia.js

190 ms

js

js

81 ms

common.js

common.js

111 ms

jquery-migrate.js

jquery-migrate.js

110 ms

owl.carousel.min.js

owl.carousel.min.js

110 ms

jquery-ui.js

jquery-ui.js

173 ms

jquery.storageapi.min.js

jquery.storageapi.min.js

155 ms

main.js

main.js

151 ms

jsonip.com

jsonip.com

135 ms

collapsible.js

collapsible.js

99 ms

underscore.js

underscore.js

66 ms

modal.js

modal.js

68 ms

knockout.js

knockout.js

57 ms

knockout-es5.js

knockout-es5.js

55 ms

scripts.js

scripts.js

41 ms

engine.js

engine.js

39 ms

bootstrap.js

bootstrap.js

39 ms

observable_array.js

observable_array.js

39 ms

bound-nodes.js

bound-nodes.js

53 ms

text.js

text.js

45 ms

key-codes.js

key-codes.js

45 ms

23.22.104.59

23.22.104.59

45 ms

knockout-repeat.js

knockout-repeat.js

23 ms

knockout-fast-foreach.js

knockout-fast-foreach.js

23 ms

observable_source.js

observable_source.js

20 ms

renderer.js

renderer.js

21 ms

console-logger.js

console-logger.js

23 ms

resizable.js

resizable.js

34 ms

i18n.js

i18n.js

34 ms

scope.js

scope.js

27 ms

range.js

range.js

43 ms

mage-init.js

mage-init.js

38 ms

keyboard.js

keyboard.js

40 ms

optgroup.js

optgroup.js

49 ms

after-render.js

after-render.js

53 ms

autoselect.js

autoselect.js

53 ms

datepicker.js

datepicker.js

60 ms

outer_click.js

outer_click.js

56 ms

fadeVisible.js

fadeVisible.js

61 ms

collapsible.js

collapsible.js

67 ms

staticChecked.js

staticChecked.js

71 ms

simple-checked.js

simple-checked.js

81 ms

bind-html.js

bind-html.js

83 ms

tooltip.js

tooltip.js

85 ms

wrapper.js

wrapper.js

84 ms

events.js

events.js

89 ms

es6-collections.js

es6-collections.js

89 ms

modal-popup.html

modal-popup.html

1733 ms

modal-slide.html

modal-slide.html

1749 ms

modal-custom.html

modal-custom.html

112 ms

js-translation.json

js-translation.json

722 ms

class.js

class.js

91 ms

local.js

local.js

99 ms

loader.js

loader.js

103 ms

logger.js

logger.js

113 ms

entry-factory.js

entry-factory.js

117 ms

console-output-handler.js

console-output-handler.js

118 ms

formatter.js

formatter.js

130 ms

message-pool.js

message-pool.js

142 ms

levels-pool.js

levels-pool.js

134 ms

logger-utils.js

logger-utils.js

147 ms

registry.js

registry.js

152 ms

async.js

async.js

157 ms

main.js

main.js

141 ms

calendar.js

calendar.js

146 ms

moment.js

moment.js

146 ms

1617 ms

tooltip.html

tooltip.html

137 ms

entry.js

entry.js

79 ms

template.js

template.js

77 ms

1529 ms

format=WEB

format=WEB

1549 ms

format=WEB

format=WEB

1631 ms

format=WEB

format=WEB

1644 ms

format=WEB

format=WEB

1713 ms

dom-observer.js

dom-observer.js

52 ms

bindings.js

bindings.js

51 ms

arrays.js

arrays.js

62 ms

compare.js

compare.js

67 ms

misc.js

misc.js

70 ms

objects.js

objects.js

82 ms

strings.js

strings.js

84 ms

jquery-ui-timepicker-addon.js

jquery-ui-timepicker-addon.js

76 ms

MutationObserver.js

MutationObserver.js

52 ms

FormData.js

FormData.js

30 ms

format=WEB

format=WEB

1646 ms

format=WEB

format=WEB

1553 ms

format=WEB

format=WEB

1621 ms

format=WEB

format=WEB

1551 ms

format=WEB

format=WEB

1605 ms

format=WEB

format=WEB

1556 ms

fit=pad

fit=pad

1547 ms

52720098987

52720098987

1594 ms

51042931809

51042931809

1587 ms

1552 ms

1588 ms

1513 ms

1517 ms

1588 ms

Accessibility Review

pcnametag.ca accessibility score

73

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

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

pcnametag.ca best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pcnametag.ca SEO score

66

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Pcnametag.ca 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 Pcnametag.ca 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

pcnametag.ca

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