Tools & Wizards About Us
hot-pot-city.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

hot-pot-city.com

Hot Pot City - Portland's place to go for Taiwanese Hot Pots

Page Load Speed

2.3 sec in total

First Response

49 ms

Resources Loaded

2 sec

Page Rendered

223 ms

hot-pot-city.com screenshot

About Website

Welcome to hot-pot-city.com homepage info - get ready to check Hot Pot City best content right away, or after learning these important things about hot-pot-city.com

If the broth and the ingredients aren't enough to overload your burnt taste buds you also get to mix up your favorite dipping sauce.

Visit hot-pot-city.com

Key Findings

We analyzed Hot-pot-city.com page load time and found that the first response time was 49 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

hot-pot-city.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value3,950 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

hot-pot-city.com

49 ms

www.hot-pot-city.com

65 ms

adsbygoogle.js

98 ms

all.css

184 ms

theme1.css

4 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 26% of them (21 requests) were addressed to the original Hot-pot-city.com, 18% (14 requests) were made to Googleads.g.doubleclick.net and 13% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.9 kB (6%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hot-pot-city.com main page is 1.1 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. 65% of websites need less resources to load. Javascripts take 774.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 44.3 kB

  • Original 52.6 kB
  • After minification 42.8 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 9.9 kB, which is 19% 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 44.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 18 B

  • Original 185.6 kB
  • After minification 185.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. Hot Pot City images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 13.2 kB

  • Original 774.4 kB
  • After minification 772.1 kB
  • After compression 761.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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 7.4 kB

  • Original 59.9 kB
  • After minification 59.3 kB
  • After compression 52.5 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. Hot-pot-city.com needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (57%)

Requests Now

65

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hot-pot-city.com

hot-pot-city.com

49 ms

www.hot-pot-city.com

www.hot-pot-city.com

65 ms

adsbygoogle.js

adsbygoogle.js

98 ms

all.css

all.css

184 ms

theme1.css

theme1.css

4 ms

jquery.min.js

jquery.min.js

19 ms

api.js

api.js

68 ms

bootstrap.min.js

bootstrap.min.js

18 ms

hover-dropdown-menu.js

hover-dropdown-menu.js

18 ms

jquery.hover-dropdown-menu-addon.js

jquery.hover-dropdown-menu-addon.js

18 ms

owl.carousel.min.js

owl.carousel.min.js

22 ms

jquery.countTo.js

jquery.countTo.js

34 ms

jquery.appear.js

jquery.appear.js

34 ms

main.js

main.js

31 ms

bootstrap.min.css

bootstrap.min.css

37 ms

hover-dropdown-menu.css

hover-dropdown-menu.css

29 ms

jquery.fancybox.css

jquery.fancybox.css

36 ms

jquery-ui.css

jquery-ui.css

50 ms

owl.carousel.css

owl.carousel.css

49 ms

owl.theme.default.css

owl.theme.default.css

49 ms

themeHover.css

themeHover.css

48 ms

css

css

69 ms

show_ads_impl.js

show_ads_impl.js

264 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

21 ms

video-back-sm.jpg

video-back-sm.jpg

17 ms

place

place

332 ms

recaptcha__en.js

recaptcha__en.js

45 ms

footer-back-1.png

footer-back-1.png

8 ms

footer-back-2.png

footer-back-2.png

7 ms

S6uyw4BMUTPHjx4wWyWtFCc.ttf

S6uyw4BMUTPHjx4wWyWtFCc.ttf

83 ms

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

84 ms

S6u8w4BMUTPHh30AXC-vNiXg7Q.ttf

S6u8w4BMUTPHh30AXC-vNiXg7Q.ttf

99 ms

S6u9w4BMUTPHh6UVSwiPHA3q5d0.ttf

S6u9w4BMUTPHh6UVSwiPHA3q5d0.ttf

108 ms

S6u9w4BMUTPHh50XSwiPHA3q5d0.ttf

S6u9w4BMUTPHh50XSwiPHA3q5d0.ttf

109 ms

rP2Hp2yn6lkG50LoCZOIGDWEBlw.ttf

rP2Hp2yn6lkG50LoCZOIGDWEBlw.ttf

128 ms

fa-solid-900.woff

fa-solid-900.woff

97 ms

fa-regular-400.woff

fa-regular-400.woff

143 ms

fa-brands-400.woff

fa-brands-400.woff

193 ms

ads

ads

669 ms

ads

ads

1190 ms

ads

ads

437 ms

ads

ads

404 ms

ads

ads

308 ms

ads

ads

329 ms

ads

ads

640 ms

ads

ads

768 ms

ads

ads

636 ms

ads

ads

919 ms

js

js

51 ms

7cd4e431960dfbc46ebf5b45a3c9c013.js

7cd4e431960dfbc46ebf5b45a3c9c013.js

4 ms

load_preloaded_resource.js

load_preloaded_resource.js

49 ms

b402b2bd027c28d5c90c17bfa425037e.js

b402b2bd027c28d5c90c17bfa425037e.js

18 ms

abg_lite.js

abg_lite.js

51 ms

window_focus.js

window_focus.js

60 ms

qs_click_protection.js

qs_click_protection.js

62 ms

ufs_web_display.js

ufs_web_display.js

43 ms

d3bea833c2cc1c58e9669317c0a4e806.js

d3bea833c2cc1c58e9669317c0a4e806.js

44 ms

icon.png

icon.png

201 ms

s

s

174 ms

css

css

39 ms

reactive_library.js

reactive_library.js

159 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyzAFyo4d4k.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyzAFyo4d4k.ttf

7 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyzAFyo4d4k.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyzAFyo4d4k.ttf

7 ms

activeview

activeview

86 ms

4DPoyt1VXFu9KUV3wfZ2z3y8g_kcb_PjstTR5ZPZl3Q.js

4DPoyt1VXFu9KUV3wfZ2z3y8g_kcb_PjstTR5ZPZl3Q.js

9 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

97 ms

css2

css2

123 ms

2442226590233105446

2442226590233105446

114 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

53 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

50 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

55 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

57 ms

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

9 ms

KFOmCnqEu92Fr1Me5WZNCzc.ttf

KFOmCnqEu92Fr1Me5WZNCzc.ttf

8 ms

sodar

sodar

106 ms

activeview

activeview

95 ms

sodar2.js

sodar2.js

5 ms

runner.html

runner.html

7 ms

aframe

aframe

37 ms

hhT7r2j7IM84IjrHPq4DliozylkjplqSUN38T7c3Pqk.js

hhT7r2j7IM84IjrHPq4DliozylkjplqSUN38T7c3Pqk.js

5 ms

Accessibility Review

hot-pot-city.com accessibility score

75

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-*] attributes do not match their roles

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

hot-pot-city.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

Page has valid source maps

SEO Factors

hot-pot-city.com 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

    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 Hot-pot-city.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 Hot-pot-city.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

hot-pot-city.com

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