Tools & Wizards About Us
brand-pride.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

brand-pride.com

Brand Pride, Inc.: Home

Page Load Speed

2.8 sec in total

First Response

44 ms

Resources Loaded

2.1 sec

Page Rendered

611 ms

brand-pride.com screenshot

About Website

Visit brand-pride.com now to see the best up-to-date Brand Pride content and also check out these interesting facts you probably never knew about brand-pride.com

Brand Pride, Inc. - Best selection of promotional items, apparel and corporate gifts.

Visit brand-pride.com

Key Findings

We analyzed Brand-pride.com page load time and found that the first response time was 44 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

brand-pride.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.21

59/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

Network Requests Diagram

brand-pride.com

44 ms

shop.brand-pride.com

1431 ms

css

35 ms

css

46 ms

css

56 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Brand-pride.com, 45% (27 requests) were made to Tscstatic.brand-pride.com and 23% (14 requests) were made to Shop.brand-pride.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Shop.brand-pride.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.9 kB (32%)

Content Size

347.1 kB

After Optimization

237.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Brand-pride.com main page is 347.1 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. 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 220.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 108.7 kB

  • Original 126.6 kB
  • After minification 95.6 kB
  • After compression 17.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 31.0 kB, which is 24% 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 108.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 408 B
  • After minification 408 B

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. Brand Pride images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 220.1 kB
  • After minification 220.1 kB
  • After compression 218.9 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.

Requests Breakdown

Number of requests can be reduced by 18 (35%)

Requests Now

52

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brand-pride.com

brand-pride.com

44 ms

shop.brand-pride.com

shop.brand-pride.com

1431 ms

css

css

35 ms

css

css

46 ms

css

css

56 ms

Core

Core

65 ms

airy

airy

101 ms

airy-product-bundle

airy-product-bundle

82 ms

GetCss

GetCss

94 ms

airy-home-bundle

airy-home-bundle

83 ms

core

core

304 ms

airy

airy

74 ms

airy-product-grid

airy-product-grid

124 ms

airy-home-bundle

airy-home-bundle

124 ms

api.js

api.js

45 ms

core.js

core.js

28 ms

js

js

66 ms

hotjar-1646832.js

hotjar-1646832.js

99 ms

logo_Y50OJNLLFM.png

logo_Y50OJNLLFM.png

370 ms

306904607

306904607

190 ms

t1HonestPr_1_OJPXLOAB70M5R6.jpg

t1HonestPr_1_OJPXLOAB70M5R6.jpg

449 ms

t1TheProfe_1_MO1YD6X1LBYFYE.jpg

t1TheProfe_1_MO1YD6X1LBYFYE.jpg

529 ms

Distinctiv_p1_l5_1_PGRWABGP4PYVT9.jpg

Distinctiv_p1_l5_1_PGRWABGP4PYVT9.jpg

447 ms

GetOutdoor_p1_l6_1_E9VJ6Q73VZJ74B.jpg

GetOutdoor_p1_l6_1_E9VJ6Q73VZJ74B.jpg

449 ms

GiveBack_p1_l7_1_175FTVI94MHQPT.jpg

GiveBack_p1_l7_1_175FTVI94MHQPT.jpg

447 ms

PremierBag_p1_l8_1_9UU2DGZY17VA2E.jpg

PremierBag_p1_l8_1_9UU2DGZY17VA2E.jpg

449 ms

SchoolSpir_p1_l9_1_8J8V5S4M9YQN0F.jpg

SchoolSpir_p1_l9_1_8J8V5S4M9YQN0F.jpg

451 ms

Athleisure_p1_l10_1_Y44XMDHFPJ0QKT.jpg

Athleisure_p1_l10_1_Y44XMDHFPJ0QKT.jpg

452 ms

Personaliz_p1_l11_1_OHSK490ANAK82X.jpg

Personaliz_p1_l11_1_OHSK490ANAK82X.jpg

450 ms

BrandtheBr_p1_l12_1_WGG26CP8QJ8FGU.jpg

BrandtheBr_p1_l12_1_WGG26CP8QJ8FGU.jpg

521 ms

SelfCare_p1_l13_1_2Y8P03FZO0A4MW.jpg

SelfCare_p1_l13_1_2Y8P03FZO0A4MW.jpg

521 ms

UniqueIdea_p1_l14_1_0EEHX51UIXP8AP.jpg

UniqueIdea_p1_l14_1_0EEHX51UIXP8AP.jpg

522 ms

WorkfromHo_p1_l15_1_2FE4YU16G4HQ93.jpg

WorkfromHo_p1_l15_1_2FE4YU16G4HQ93.jpg

522 ms

WomenInspi_p1_l16_1_ODDL8RW8JWO83K.jpg

WomenInspi_p1_l16_1_ODDL8RW8JWO83K.jpg

524 ms

Asi49427135_300x.jpg

Asi49427135_300x.jpg

522 ms

Asi48979775_300x.jpg

Asi48979775_300x.jpg

523 ms

Asi305126454_300x.jpg

Asi305126454_300x.jpg

525 ms

Asi49335773_300x.jpg

Asi49335773_300x.jpg

524 ms

Asi48546566_300x.jpg

Asi48546566_300x.jpg

525 ms

Asi306515218_300x.jpg

Asi306515218_300x.jpg

526 ms

Asi49330159_300x.jpg

Asi49330159_300x.jpg

526 ms

Asi48926934_300x.jpg

Asi48926934_300x.jpg

527 ms

Asi49330144_300x.jpg

Asi49330144_300x.jpg

533 ms

Asi302865932_300x.jpg

Asi302865932_300x.jpg

535 ms

Asi49428909_300x.jpg

Asi49428909_300x.jpg

534 ms

Asi47722181_300x.jpg

Asi47722181_300x.jpg

535 ms

MarkKessler-portrait-RCVH.png

MarkKessler-portrait-RCVH.png

178 ms

JordanPayne-portrait-AWQZ.png

JordanPayne-portrait-AWQZ.png

443 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

66 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

89 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

69 ms

746747120-1399a088e4a6edb92bf650b094d7d22ed27a3e4fb6c5ef014aadb99f7e4fc4b8-d

746747120-1399a088e4a6edb92bf650b094d7d22ed27a3e4fb6c5ef014aadb99f7e4fc4b8-d

211 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

185 ms

flaticon.woff

flaticon.woff

169 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

121 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

183 ms

recaptcha__en.js

recaptcha__en.js

187 ms

js

js

68 ms

analytics.js

analytics.js

131 ms

collect

collect

64 ms

Accessibility Review

brand-pride.com accessibility score

74

Accessibility Issues

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible 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.

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 [lang] attribute

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

brand-pride.com 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

Missing source maps for large first-party JavaScript

SEO Factors

brand-pride.com SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brand-pride.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 Brand-pride.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

brand-pride.com

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