25.2 sec in total
1.2 sec
23.3 sec
652 ms
Visit buildingin.com now to see the best up-to-date Buildingin content for South Korea and also check out these interesting facts you probably never knew about buildingin.com
표류청춘(Ver3.8)
Visit buildingin.comWe analyzed Buildingin.com page load time and found that the first response time was 1.2 sec and then it took 23.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
buildingin.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value6.3 s
11/100
25%
Value4.2 s
78/100
10%
Value520 ms
56/100
30%
Value0.078
95/100
15%
Value8.2 s
40/100
10%
1216 ms
1251 ms
1039 ms
1043 ms
1042 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Buildingin.com, 44% (57 requests) were made to S1.daumcdn.net and 14% (18 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Static.hanrss.com.
Page size can be reduced by 263.4 kB (15%)
1.8 MB
1.5 MB
In fact, the total size of Buildingin.com main page is 1.8 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 137.2 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 17.5 kB, which is 11% 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 137.2 kB or 85% of the original size.
Potential reduce by 71.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. Buildingin images are well optimized though.
Potential reduce by 35.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 35.0 kB or 43% of the original size.
Potential reduce by 19.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. Buildingin.com needs all CSS files to be minified and compressed as it can save up to 19.8 kB or 84% of the original size.
Number of requests can be reduced by 71 (55%)
128
57
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buildingin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
buildingin.com
1216 ms
style.css
1251 ms
shareEntryWithSNS.css
1039 ms
shareEntryWithSNS.js
1043 ms
lightbox.min.css
1042 ms
style.css
1043 ms
profile.js
1264 ms
jigu-latest.min.js
2196 ms
T.js
1245 ms
EAF2.js
1487 ms
common.js
1754 ms
gallery.js
1462 ms
flash.js
1451 ms
PHON.js
1498 ms
sha256.js
1709 ms
md5.min.js
1722 ms
swfobject.js
1732 ms
dialog.css
2541 ms
reset.css
1937 ms
tabloid.css
2452 ms
items.css
2225 ms
util.css
1995 ms
tistory-grid-min.css
2611 ms
items.js
2235 ms
menubar.css
2390 ms
682 ms
swfob.js
2202 ms
functions.js
2201 ms
searchDragSelection.js
2339 ms
lightbox.min.js
2429 ms
roosevelt_dk_bt.js
281 ms
check.php
274 ms
2444B53D54E0DE6923D47B
2301 ms
262D0F3A54CE11C904D761
1893 ms
2369DA48543B36CA2A7437
2423 ms
2762494753DBDE6D2F0A2E
3632 ms
246A153753D656130F6703
1890 ms
2772793353204DFF042690
2014 ms
27348D4152CBA75635FB83
1461 ms
26696B4352C391BD2F9556
4031 ms
2453C8365692816E26F094
1606 ms
2120ED39549FB4162983B1
1647 ms
2606004853B542000F620E
1469 ms
2722903B53A7F4951DA795
2196 ms
2436D43A532AF6001F27A9
1195 ms
1212BA3F511DF63A0B426B
1039 ms
1327A43450659C69176402
1659 ms
201F704C4E8B01400F68AC
1865 ms
ico_view_new.gif
716 ms
favicon.ico
63 ms
add_to_hanrss5.gif
19671 ms
263BD533530CAC922C9F4C
1777 ms
2622B440533431B00AA1A8
2025 ms
23117D4D531B53323D9AEC
2063 ms
1754994150741F5712C253
1482 ms
15224C425061AF9C227D63
1516 ms
ico_twitter.gif
714 ms
tab_top.gif
713 ms
tab_isleaf.gif
709 ms
tab_closed.gif
712 ms
navi_back_active.gif
714 ms
tab_treed.gif
718 ms
tab_treed_end.gif
722 ms
navi_back_active_end.gif
723 ms
2369DA48543B36CA2A7437
1445 ms
2064113C5167DE7A061DE7
2273 ms
2066294C4FE82D38258770
1822 ms
262D0F3A54CE11C904D761
1162 ms
1944244B4E5A15621FE906
2058 ms
close.png
228 ms
loading.gif
226 ms
prev.png
225 ms
next.png
226 ms
btn_rss.gif
234 ms
23467048533D6B312C52B2
1891 ms
221BFE47533430481B38F9
2077 ms
2776113E534BF160013695
1623 ms
242495415320321501D7FE
1396 ms
211AB74552E9F7A6103039
4022 ms
2762494753DBDE6D2F0A2E
2293 ms
260F404952F65C80159093
2063 ms
166B07415062B0402447E6
1485 ms
2444B53D54E0DE6923D47B
1769 ms
242FDA3453121C3A1455A8
1917 ms
2352DD415237FB61349D0B
1819 ms
253F743951FFBD3A04F800
2010 ms
241E504F51F3A69E1E9025
4136 ms
266E363E5251787E210E83
1877 ms
212E4B4051DDAD62145270
1876 ms
23744F3354C4F40D18E6CB
1299 ms
116C52394EFEC67B281B84
1297 ms
2477A54F51383FEE0F4C82
1614 ms
257A964F5534AA631D36E4
3164 ms
png.png
747 ms
g1_1.gif
708 ms
g1_0.gif
708 ms
box_topleft.gif
222 ms
box_top_line.gif
413 ms
box_toprig.gif
418 ms
box_left_line.gif
431 ms
box_rig_line.gif
422 ms
main.jpg
658 ms
wrap_menu_t.gif
444 ms
wrap_menu_m.gif
630 ms
wrap_menu_bo.gif
639 ms
sidebarbg_img.gif
643 ms
bg_comment_bg1.png
706 ms
bg_comment_bg2.png
706 ms
ico_dotted.gif
705 ms
bg_sidebar_b2.png
706 ms
bt_plus.gif
710 ms
pbox_topleft.gif
622 ms
pbox_top_line.gif
620 ms
pbox_toprig.gif
831 ms
pbox_left_line.gif
839 ms
pbox_rig_line.gif
845 ms
pbox_botleft.gif
854 ms
pbox_bot_line.gif
847 ms
pbox_botrig.gif
852 ms
icon_sidebar_notice.gif
1092 ms
btn_search.gif
1022 ms
tab_opened.gif
627 ms
bullet_dot.gif
990 ms
box_botleft.gif
1015 ms
box_bot_line.gif
1442 ms
box_botrig.gif
1462 ms
jquery.min.js
120 ms
td.min.js
1974 ms
257A964F5534AA631D36E4
722 ms
footsteps
1781 ms
buildingin.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
buildingin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
buildingin.com SEO score
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 uses legible font sizes
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buildingin.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Buildingin.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.
buildingin.com
Open Graph data is detected on the main page of Buildingin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: