Tools & Wizards About Us
hitank.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hitank.com

SERIM MULSAN

Page Load Speed

14 sec in total

First Response

851 ms

Resources Loaded

13 sec

Page Rendered

158 ms

hitank.com screenshot

About Website

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

Water that humans need to live! SERIM MULSAN will make efforts to supply safe water tanks through continuous research and development for safe water management.

Visit hitank.com

Key Findings

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

Performance Metrics

hitank.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

hitank.com

851 ms

default.css

579 ms

reset.css

394 ms

headStyle.css

400 ms

footerStyle.css

401 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 65% of them (53 requests) were addressed to the original Hitank.com, 23% (19 requests) were made to Errdoc.gabia.io and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (9.6 sec) belongs to the original domain Hitank.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 328.5 kB (53%)

Content Size

614.3 kB

After Optimization

285.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hitank.com main page is 614.3 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. 30% of websites need less resources to load. CSS take 242.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 16.8 kB

  • Original 20.6 kB
  • After minification 16.9 kB
  • After compression 3.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 3.7 kB, which is 18% 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 16.8 kB or 81% of the original size.

Image Optimization

-8%

Potential reduce by 17.6 kB

  • Original 217.9 kB
  • After minification 200.3 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. Hitank images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 91.3 kB

  • Original 133.7 kB
  • After minification 119.7 kB
  • After compression 42.4 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 91.3 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 202.9 kB

  • Original 242.1 kB
  • After minification 209.2 kB
  • After compression 39.2 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. Hitank.com needs all CSS files to be minified and compressed as it can save up to 202.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (47%)

Requests Now

55

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hitank. 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 21 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hitank.com

hitank.com

851 ms

default.css

default.css

579 ms

reset.css

reset.css

394 ms

headStyle.css

headStyle.css

400 ms

footerStyle.css

footerStyle.css

401 ms

mainStyle.css

mainStyle.css

414 ms

introduce.css

introduce.css

610 ms

directions.css

directions.css

785 ms

gallery_table.css

gallery_table.css

792 ms

webzine_table.css

webzine_table.css

806 ms

bs_info.css

bs_info.css

808 ms

bs_area.css

bs_area.css

1359 ms

slick.css

slick.css

992 ms

common.css

common.css

1178 ms

basic_table.css

basic_table.css

1185 ms

contact_us.css

contact_us.css

1191 ms

qa.css

qa.css

1194 ms

faq.css

faq.css

1418 ms

swiper.min.css

swiper.min.css

30 ms

animate.css

animate.css

2137 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1980 ms

jquery.menu.js

jquery.menu.js

1586 ms

common.js

common.js

1815 ms

wrest.js

wrest.js

1762 ms

placeholders.min.js

placeholders.min.js

1830 ms

site.js

site.js

1983 ms

sub.js

sub.js

2169 ms

slick.js

slick.js

2210 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

2224 ms

swiper.min.js

swiper.min.js

44 ms

wow.min.js

wow.min.js

45 ms

font-awesome.min.css

font-awesome.min.css

2573 ms

css

css

31 ms

404.html

404.html

586 ms

404.html

404.html

412 ms

404.html

404.html

396 ms

404.html

404.html

417 ms

t_logo01.png

t_logo01.png

247 ms

main01-1.jpg

main01-1.jpg

1229 ms

main01-2.jpg

main01-2.jpg

1452 ms

b_logo.png

b_logo.png

459 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2266 ms

noto-sans-kr-v11-latin-700.woff

noto-sans-kr-v11-latin-700.woff

417 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01SLPg9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01SLPg9w.woff

31 ms

noto-sans-kr-v11-latin-900.woff

noto-sans-kr-v11-latin-900.woff

623 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1SLPg9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1SLPg9w.woff

204 ms

noto-sans-kr-v11-latin-regular.woff

noto-sans-kr-v11-latin-regular.woff

822 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLPg9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLPg9w.woff

204 ms

noto-sans-kr-v11-latin-300.woff

noto-sans-kr-v11-latin-300.woff

826 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQySLPg9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQySLPg9w.woff

360 ms

noto-sans-kr-v11-latin-100.woff

noto-sans-kr-v11-latin-100.woff

1023 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozSLPg9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozSLPg9w.woff

358 ms

gnb_bg2.gif

gnb_bg2.gif

1242 ms

main01.jpg

main01.jpg

9619 ms

ft_sns3.png

ft_sns3.png

1431 ms

ft_sns4.png

ft_sns4.png

1595 ms

404.html

404.html

203 ms

404.html

404.html

203 ms

noto-sans-kr-v11-latin-700.ttf

noto-sans-kr-v11-latin-700.ttf

1003 ms

404.html

404.html

208 ms

404.html

404.html

207 ms

noto-sans-kr-v11-latin-900.ttf

noto-sans-kr-v11-latin-900.ttf

1005 ms

404.html

404.html

210 ms

noto-sans-kr-v11-latin-regular.ttf

noto-sans-kr-v11-latin-regular.ttf

797 ms

noto-sans-kr-v11-latin-300.ttf

noto-sans-kr-v11-latin-300.ttf

981 ms

noto-sans-kr-v11-latin-100.ttf

noto-sans-kr-v11-latin-100.ttf

814 ms

404.html

404.html

207 ms

404.html

404.html

207 ms

404.html

404.html

205 ms

noto-sans-kr-v11-latin-700.svg

noto-sans-kr-v11-latin-700.svg

411 ms

404.html

404.html

204 ms

noto-sans-kr-v11-latin-regular.svg

noto-sans-kr-v11-latin-regular.svg

395 ms

noto-sans-kr-v11-latin-900.svg

noto-sans-kr-v11-latin-900.svg

398 ms

404.html

404.html

207 ms

noto-sans-kr-v11-latin-300.svg

noto-sans-kr-v11-latin-300.svg

220 ms

404.html

404.html

208 ms

noto-sans-kr-v11-latin-100.svg

noto-sans-kr-v11-latin-100.svg

620 ms

404.html

404.html

214 ms

404.html

404.html

204 ms

404.html

404.html

212 ms

404.html

404.html

203 ms

Accessibility Review

hitank.com accessibility score

56

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.

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

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

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

High

Page has valid source maps

SEO Factors

hitank.com SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

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

    EN

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hitank.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Hitank.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

hitank.com

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