10 sec in total
1.5 sec
8.2 sec
357 ms
Click here to check amazing FUN Arch Tistory content for South Korea. Otherwise, check out these important facts you probably never knew about funarch.tistory.com
재미있는 건축+도시+철학+사진+커피 e-mail : zptloves@naver.com
Visit funarch.tistory.comWe analyzed Funarch.tistory.com page load time and found that the first response time was 1.5 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
funarch.tistory.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value8.1 s
2/100
25%
Value6.6 s
38/100
10%
Value40 ms
100/100
30%
Value0.024
100/100
15%
Value7.0 s
53/100
10%
1486 ms
640 ms
431 ms
432 ms
642 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Funarch.tistory.com, 38% (49 requests) were made to S1.daumcdn.net and 5% (6 requests) were made to Cfile27.uf.tistory.com. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Widgetprovider.daum.net.
Page size can be reduced by 282.7 kB (25%)
1.1 MB
866.8 kB
In fact, the total size of Funarch.tistory.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. 40% of websites need less resources to load. Images take 792.4 kB which makes up the majority of the site volume.
Potential reduce by 83.6 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 15.2 kB, which is 15% 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 83.6 kB or 83% of the original size.
Potential reduce by 9.0 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. FUN Arch Tistory images are well optimized though.
Potential reduce by 170.5 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 170.5 kB or 73% of the original size.
Potential reduce by 19.6 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. Funarch.tistory.com needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 81% of the original size.
Number of requests can be reduced by 47 (38%)
123
76
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUN Arch Tistory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
funarch.tistory.com
1486 ms
style.css
640 ms
lightbox.min.css
431 ms
style.css
432 ms
profile.js
642 ms
t_livere_lib.js
584 ms
t_livere.js
586 ms
livere_tistory.js
578 ms
jigu-latest.min.js
837 ms
T.js
489 ms
EAF2.js
848 ms
common.js
1114 ms
gallery.js
723 ms
flash.js
831 ms
PHON.js
833 ms
sha256.js
1006 ms
md5.min.js
1092 ms
swfobject.js
1097 ms
dialog.css
1090 ms
reset.css
1091 ms
tabloid.css
1763 ms
items.css
1316 ms
util.css
1321 ms
tistory-grid-min.css
1376 ms
items.js
1143 ms
menubar.css
1162 ms
rainbow.js
1370 ms
view
6302 ms
functions.js
1146 ms
searchDragSelection.js
1186 ms
lightbox.min.js
1187 ms
roosevelt_dk_bt.js
45 ms
jquery.min.js
56 ms
check.php
344 ms
2213D840545053D20E45CC
2987 ms
246DB7455663AE581604C2
2265 ms
251E8A3F55EE787824DE2B
1529 ms
26448440563C2F8E1F7754
913 ms
232BAA4D55E901AD36C586
1359 ms
23489A4C55E552F61BC622
1482 ms
272530335595D1790F3CF2
1159 ms
22406A4C5590B06D095A2C
1486 ms
2529093C558263ED33C3BD
1253 ms
27343B4D55825A0C2CB96F
1848 ms
242F534255821B2D04963E
1945 ms
2612BB395570F1B52A56EC
1701 ms
23457544556FB76E133619
1919 ms
250F09505568266F2634EF
1396 ms
250B6B4B5553153420E433
1870 ms
24263B405549A5A62EB8C5
1458 ms
22110C455549A4DF06B610
1358 ms
256F563A55E937E2070CFC
1145 ms
2755D23F5590C8D713D42F
1988 ms
2777B0435590C83326C1A8
1461 ms
224AB535552DC35C1C706E
658 ms
2756CC4F542B58E021C5C7
1999 ms
213D1442534F22CD2171D5
1835 ms
21434F40534E318A01C522
1870 ms
2622993554ADCFCF21E9D4
1361 ms
250BCA3754ADCD210FDA03
1584 ms
244559415372B552254B08
1580 ms
24384B3D534E32841A9D91
1366 ms
271A593B5553F06A1A121F
2102 ms
224EED48559A2F22081C35
1861 ms
close.png
205 ms
loading.gif
436 ms
prev.png
240 ms
next.png
207 ms
2355DB425570F314355041
1424 ms
234C1E47556FB5113845A6
1453 ms
24547945557151463B892D
1249 ms
261BB647542B59E6029623
1470 ms
2425AE37532CF76311A445
1489 ms
2213683855838F732271E7
1134 ms
262F683D557663320E759C
1341 ms
2603143B53C37CE510DFF7
1442 ms
267F0C3A556F9EB0349F86
1410 ms
2345DD40534E323404FC64
1659 ms
274D8E43552B66C409B954
1421 ms
242FAA3554ADCEDC19338E
1432 ms
2371E43B53C37C88294BD9
1690 ms
2425FC3A556FF72924DDC4
1282 ms
24262A38556FF5C4050546
1301 ms
24146E40556FB16121E77A
1093 ms
235C543B54ADCF4922C2C4
1341 ms
2644954355C977092D9D99
2208 ms
2176F24655715052275C6A
1661 ms
246BE64C556FD71219586C
1639 ms
241B1F40556FB28D24BA77
1783 ms
2666FB465590C95919550A
1832 ms
2577F74754ADD32428164E
1601 ms
2344873555E9376A056D89
1307 ms
2534E9485583A6CE159075
1484 ms
241925375570F0DD22A5C0
1631 ms
246B7A47559C798E304E9E
1826 ms
231A8F43557150C336EAC8
1621 ms
2359C145552B65FF18D321
1636 ms
2408D63354ADCE411DCA19
1652 ms
255C954C554C994A244157
1670 ms
2150FC415590CA3E3262EA
1447 ms
2208D23F55ED52D523FA64
1678 ms
226CA9435590C9E1363400
1642 ms
2261963F534E32C7317364
1656 ms
2540EA40534E31EC2E1D72
1654 ms
253E043954B4CCE306B4D5
1455 ms
222CB93A53C37D3B0BA00D
1455 ms
menu_home.gif
217 ms
menu_bar.gif
217 ms
menu_tag.gif
388 ms
menu_guest.gif
384 ms
menu_admin.gif
478 ms
menu_write.gif
426 ms
btn_search.gif
424 ms
h3_category.gif
600 ms
bul_category.gif
597 ms
bg_counter.gif
612 ms
88x31.png
100 ms
print.css
246 ms
1761E24D4E461BD028F893
254 ms
h3_notice.gif
215 ms
h3_mylink.gif
229 ms
h3_calendar.gif
246 ms
btn_cal_prev.gif
220 ms
btn_cal_next.gif
218 ms
bg_footer.gif
257 ms
btn_rss.gif
424 ms
bar_footermenu.gif
424 ms
td.min.js
510 ms
funarch.tistory.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
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>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
funarch.tistory.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
funarch.tistory.com SEO score
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 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 Funarch.tistory.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 Funarch.tistory.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.
funarch.tistory.com
Open Graph data is detected on the main page of FUN Arch Tistory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: