56.6 sec in total
3.1 sec
53.1 sec
482 ms
Welcome to home336.com homepage info - get ready to check Home336 best content right away, or after learning these important things about home336.com
상생하는 부동산경매. 홈336입니다.
Visit home336.comWe analyzed Home336.com page load time and found that the first response time was 3.1 sec and then it took 53.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
home336.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value5.3 s
22/100
25%
Value16.1 s
0/100
10%
Value680 ms
44/100
30%
Value0.312
37/100
15%
Value86.6 s
0/100
10%
3112 ms
1559 ms
38 ms
432 ms
442 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 83% of them (86 requests) were addressed to the original Home336.com, 4% (4 requests) were made to Maps.google.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Home336.com.
Page size can be reduced by 1.3 MB (51%)
2.6 MB
1.3 MB
In fact, the total size of Home336.com main page is 2.6 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 34.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. 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 34.9 kB or 79% of the original size.
Potential reduce by 34.9 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. Home336 images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 74% of the original size.
Potential reduce by 127.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. Home336.com needs all CSS files to be minified and compressed as it can save up to 127.7 kB or 83% of the original size.
Number of requests can be reduced by 52 (54%)
96
44
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Home336. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.home336.com
3112 ms
style.css
1559 ms
js
38 ms
widget.css
432 ms
anythingslider.css
442 ms
colorbox.css
443 ms
jquery.fancybox-1.3.4.css
531 ms
comments.css
797 ms
contact.css
847 ms
hoverZoom.css
1004 ms
adipoli.css
1110 ms
prettySociable.css
1389 ms
settings.css
1740 ms
captions.css
1519 ms
css3_black.css
1528 ms
jquery.js
2853 ms
jquery-migrate.min.js
1942 ms
jquery-ui-1.8.16.custom.min.js
3443 ms
html5.js
2211 ms
jquery.masonry.js
2562 ms
jquery.anythingslider.fx.min.js
2623 ms
jquery.anythingslider.min.js
3282 ms
jquery.easing.1.3.js
3066 ms
jquery.ImageSwitch.yui.js
3055 ms
jquery.colorbox-min.js
3274 ms
jquery.fancybox-1.3.4.js
4196 ms
jquery.infieldlabel.js
3548 ms
jquery.scroll-to.js
3693 ms
hover.zoom.js
3761 ms
jquery.adipoli.js
5456 ms
jquery.prettySociable.js
3944 ms
script.js
4925 ms
jquery.themepunch.plugins.min.js
4461 ms
jquery.themepunch.revolution.min.js
4984 ms
ux_style.css
4570 ms
cufon-yui.js
4984 ms
jquery.scrollTo-min.js
4956 ms
wcslog.js
251 ms
ux_common.js
4842 ms
NanumGothic_600.font.js
19877 ms
comment-reply.min.js
5004 ms
wp-embed.min.js
5116 ms
wp-emoji-release.min.js
4925 ms
style.css
4989 ms
nanumgothic.css
78 ms
common.js
38 ms
util.js
97 ms
stats.js
96 ms
AuthenticationService.Authenticate
287 ms
m
726 ms
gtm.js
116 ms
analytics.js
35 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_home3361.png
527 ms
ico_search30.png
531 ms
menu-arrow.png
540 ms
ico_fb30.png
561 ms
ico_tw30.png
577 ms
ico_rss30.png
576 ms
estimate.jpg
918 ms
%EC%82%AC%EB%B3%B8-%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_%EC%98%A5%EB%B0%94%EB%9E%8C%EC%A2%85%EA%B0%95%EC%82%AC%EC%A7%84.jpg
4307 ms
%EC%82%AC%EB%B3%B8-IMG_1497.jpg
3669 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_%EC%82%AC%EC%A7%84-12.-10.-27.-%EC%98%A4%EC%A0%84-11-54-22.jpg
7111 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_IMG_0134.jpg
7370 ms
%EC%82%AC%EB%B3%B8-%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_%EA%B2%BD%EB%A7%A4%EB%B2%95%EC%9B%90%EC%9E%85%EC%B0%B0.jpg
4174 ms
IMG_9502_1.jpg
5931 ms
%EC%A0%84%EC%97%85%EB%B6%80%EB%8F%99%EC%82%B0%EA%B2%BD%EB%A7%A4-150x150.jpg
4185 ms
%EB%B6%80%EB%8F%99%EC%82%B0%EA%B2%BD%EB%A7%A4-%EB%8F%84%EC%84%9C-2-150x150.gif
4974 ms
yay8497836-150x150.jpg
6502 ms
1200-150x150.jpg
6129 ms
%EC%A0%84%EC%84%B8%EA%B8%88-%EC%95%88%EC%A0%84%ED%95%98%EA%B2%8C-%EC%A7%80%ED%82%A4%EB%8A%94-%EB%B2%95_%EC%A0%84%EC%9E%85%EC%8B%A0%EA%B3%A0-%ED%99%95%EC%A0%95%EC%9D%BC%EC%9E%902-150x150.jpg
5497 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_1IMG_0134.jpg
8297 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_IMG_0223.jpg
8536 ms
%ED%81%AC%EA%B8%B0%EB%B3%80%ED%99%98_%EC%82%AC%EC%A7%84-12.-10.-25.-%EC%98%A4%ED%9B%84-3-29-22.jpg
9380 ms
index.php
7200 ms
NanumGothic-Regular.woff
253 ms
NanumGothic-Bold.woff
379 ms
NanumGothic-ExtraBold.woff
589 ms
linkid.js
62 ms
stripe-pattern.png
7513 ms
count.js
178 ms
admin-ajax.php
10758 ms
border1.png
7513 ms
border2.png
7584 ms
loading.gif
7869 ms
facebook.png
8060 ms
twitter.png
8139 ms
delicious.png
8380 ms
digg.png
8504 ms
linkedin.png
8519 ms
reddit.png
8881 ms
stumbleupon.png
8885 ms
tumblr.png
8911 ms
timer.png
9081 ms
collect
24 ms
collect
252 ms
loader.gif
8911 ms
shadow2.png
9147 ms
jquery-ui-1.9.2.custom.css
3677 ms
home.css
2923 ms
jquery-1.9.0.min.js
4763 ms
jquery-ui-1.9.2.custom.js
20050 ms
large_left.png
3120 ms
large_right.png
3408 ms
home336.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
home336.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
home336.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Home336.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Home336.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.
home336.com
Open Graph data is detected on the main page of Home336. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: