Tools & Wizards About Us
hommy.com screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

hommy.com

Ice Cream Machine,Ice Cream Maker Manufacturers | Hommy

Page Load Speed

4.1 sec in total

First Response

101 ms

Resources Loaded

3.7 sec

Page Rendered

330 ms

hommy.com screenshot

About Website

Click here to check amazing Hommy content. Otherwise, check out these important facts you probably never knew about hommy.com

Established in 1999,Hommy is a professional high-tech enterprise specialized in manufacturing all kinds of cooling product and food processing machine such as commercial ice cream machine and ice crea...

Visit hommy.com

Key Findings

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

Performance Metrics

hommy.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.236

53/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

www.hommy.com

101 ms

partytown.js

8 ms

base.css

23 ms

index.html.css

38 ms

base.js

95 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 27% of them (6 requests) were addressed to the original Hommy.com, 50% (11 requests) were made to Img80002414.weyesimg.com and 9% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (756 ms) relates to the external source Js.users.51.la.

Page Optimization Overview & Recommendations

Page size can be reduced by 155.6 kB (40%)

Content Size

390.9 kB

After Optimization

235.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hommy.com main page is 390.9 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. 50% of websites need less resources to load. HTML takes 133.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 111.5 kB

  • Original 133.4 kB
  • After minification 101.4 kB
  • After compression 21.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 32.1 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 111.5 kB or 84% of the original size.

Image Optimization

-54%

Potential reduce by 43.8 kB

  • Original 81.4 kB
  • After minification 37.6 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, Hommy needs image optimization as it can save up to 43.8 kB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 39 B

  • Original 130.0 kB
  • After minification 130.0 kB
  • After compression 130.0 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 273 B

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

Requests Breakdown

Number of requests can be reduced by 5 (25%)

Requests Now

20

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hommy.com

www.hommy.com

101 ms

partytown.js

partytown.js

8 ms

base.css

base.css

23 ms

index.html.css

index.html.css

38 ms

base.js

base.js

95 ms

index.html.js

index.html.js

134 ms

js

js

204 ms

19591093.js

19591093.js

756 ms

js

js

341 ms

15532193595207.png

15532193595207.png

225 ms

16027484835758.jpg

16027484835758.jpg

316 ms

16418911894948.jpg

16418911894948.jpg

320 ms

16418912077531.jpg

16418912077531.jpg

318 ms

16418912172171.jpg

16418912172171.jpg

318 ms

16418912274355.jpg

16418912274355.jpg

319 ms

16653925647151.jpg

16653925647151.jpg

320 ms

15532193595207.png

15532193595207.png

333 ms

lang_flag2.png

lang_flag2.png

297 ms

15532356048052.png

15532356048052.png

217 ms

15532356014334.png

15532356014334.png

216 ms

15532355978886.png

15532355978886.png

216 ms

HelveticaNeueLTPro-ThEx.woff2

HelveticaNeueLTPro-ThEx.woff2

7 ms

Accessibility Review

hommy.com accessibility score

58

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

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

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

hommy.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hommy.com SEO score

82

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

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

hommy.com

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