Tools & Wizards About Us
brandz13.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

brandz13.com

HOME

Page Load Speed

3.5 sec in total

First Response

90 ms

Resources Loaded

2.6 sec

Page Rendered

767 ms

brandz13.com screenshot

About Website

Visit brandz13.com now to see the best up-to-date Brandz 13 content and also check out these interesting facts you probably never knew about brandz13.com

Visit brandz13.com

Key Findings

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

Performance Metrics

brandz13.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value2,890 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

brandz13.com

90 ms

t.js

55 ms

viewer.css

130 ms

viewer.js

130 ms

842dbd63ea8e4e8da55ee8a5ee0666c3.js

410 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 37% of them (13 requests) were addressed to the original Brandz13.com, 14% (5 requests) were made to Gstatic.com and 9% (3 requests) were made to Storage.googleapis.com. The less responsive or slowest element that took the longest time to load (883 ms) relates to the external source Webzaitest.blob.core.windows.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 367.9 kB (9%)

Content Size

4.0 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Brandz13.com main page is 4.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. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 259.0 kB

  • Original 286.4 kB
  • After minification 286.4 kB
  • After compression 27.4 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 259.0 kB or 90% of the original size.

Image Optimization

-3%

Potential reduce by 107.8 kB

  • Original 3.5 MB
  • After minification 3.4 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. Brandz 13 images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 217.4 kB
  • After minification 217.3 kB
  • After compression 216.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 15 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.3 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. Brandz13.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (14%)

Requests Now

28

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

brandz13.com

brandz13.com

90 ms

t.js

t.js

55 ms

viewer.css

viewer.css

130 ms

viewer.js

viewer.js

130 ms

842dbd63ea8e4e8da55ee8a5ee0666c3.js

842dbd63ea8e4e8da55ee8a5ee0666c3.js

410 ms

26fec881560a4360b98907c37275deb2.js

26fec881560a4360b98907c37275deb2.js

491 ms

98650cbf3e0a450582bf5c0648cc29f2.js

98650cbf3e0a450582bf5c0648cc29f2.js

489 ms

localize.uat.mywebsitebuilder.com

localize.uat.mywebsitebuilder.com

369 ms

api.js

api.js

661 ms

251 ms

358 ms

335 ms

264 ms

331 ms

266 ms

267 ms

336 ms

333 ms

361 ms

355 ms

355 ms

ALyKWGaVsEemWmMSYxY8yg.woff

ALyKWGaVsEemWmMSYxY8yg.woff

632 ms

Megrim.ttf

Megrim.ttf

732 ms

webzai-icons.woff

webzai-icons.woff

883 ms

JYwDjrpa8U6xfI7FKlWegw.woff

JYwDjrpa8U6xfI7FKlWegw.woff

510 ms

recaptcha__en.js

recaptcha__en.js

36 ms

fallback

fallback

42 ms

fallback__ltr.css

fallback__ltr.css

5 ms

payload

payload

28 ms

css

css

32 ms

logo_48.png

logo_48.png

4 ms

refresh_black.png

refresh_black.png

4 ms

audio_black.png

audio_black.png

8 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

23 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

27 ms

Accessibility Review

brandz13.com accessibility score

55

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.

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

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

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

brandz13.com best practices score

75

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

SEO Factors

brandz13.com SEO score

77

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

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brandz13.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Brandz13.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

brandz13.com

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