Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

huzz.us

huzz.us

Page Load Speed

2.3 sec in total

First Response

612 ms

Resources Loaded

1.2 sec

Page Rendered

468 ms

huzz.us screenshot

About Website

Visit huzz.us now to see the best up-to-date Huzz content and also check out these interesting facts you probably never knew about huzz.us

brazen parrot decided to annoy lazy cat

Visit huzz.us

Key Findings

We analyzed Huzz.us page load time and found that the first response time was 612 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

huzz.us performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value39.9 s

0/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

huzz.us

612 ms

wp-emoji-release.min.js

85 ms

style.css

60 ms

css

15 ms

css

29 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 96% of them (55 requests) were addressed to the original Huzz.us, 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (612 ms) belongs to the original domain Huzz.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 463.6 kB (34%)

Content Size

1.4 MB

After Optimization

909.2 kB

In fact, the total size of Huzz.us main page is 1.4 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. 55% of websites need less resources to load. Images take 823.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 40.1 kB

  • Original 46.9 kB
  • After minification 42.8 kB
  • After compression 6.8 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 40.1 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 26.4 kB

  • Original 823.8 kB
  • After minification 797.4 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. Huzz images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 138.5 kB

  • Original 202.7 kB
  • After minification 201.2 kB
  • After compression 64.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 138.5 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 258.7 kB

  • Original 299.4 kB
  • After minification 280.8 kB
  • After compression 40.7 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. Huzz.us needs all CSS files to be minified and compressed as it can save up to 258.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (44%)

Requests Now

55

After Optimization

31

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

Accessibility Review

huzz.us accessibility score

68

Accessibility Issues

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

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

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

huzz.us best practices score

75

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

Browser errors were logged to the console

SEO Factors

huzz.us SEO score

100

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Huzz.us 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), while the claimed language is English. Our system also found out that Huzz.us 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

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