26 sec in total
912 ms
24.2 sec
893 ms
Visit 100mirror.com now to see the best up-to-date 100 Mirror content for South Korea and also check out these interesting facts you probably never knew about 100mirror.com
<Motor & Life 전문 블로거>
Visit 100mirror.comWe analyzed 100mirror.com page load time and found that the first response time was 912 ms and then it took 25.1 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.
100mirror.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value8.5 s
1/100
25%
Value7.6 s
25/100
10%
Value30 ms
100/100
30%
Value0.012
100/100
15%
Value7.4 s
48/100
10%
912 ms
1648 ms
80 ms
19 ms
18 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 100mirror.com, 28% (41 requests) were made to S1.daumcdn.net and 13% (19 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (15.5 sec) relates to the external source Static.tpmn.co.kr.
Page size can be reduced by 450.3 kB (20%)
2.3 MB
1.9 MB
In fact, the total size of 100mirror.com main page is 2.3 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 126.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. 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 126.2 kB or 83% of the original size.
Potential reduce by 72.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. 100 Mirror images are well optimized though.
Potential reduce by 226.1 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 226.1 kB or 63% of the original size.
Potential reduce by 25.4 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. 100mirror.com needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 80% of the original size.
Number of requests can be reduced by 72 (52%)
138
66
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 100 Mirror. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
100mirror.com
912 ms
style.css
1648 ms
css
80 ms
jsapi
19 ms
jquery.min.js
18 ms
shareEntryWithSNS.css
1395 ms
shareEntryWithSNS.js
1391 ms
addDurl.js
671 ms
lightbox.min.css
1412 ms
post_list.css
482 ms
style.css
1414 ms
profile.js
1676 ms
jigu-latest.min.js
2351 ms
T.js
1638 ms
EAF2.js
1914 ms
common.js
2209 ms
gallery.js
1878 ms
flash.js
1879 ms
PHON.js
1918 ms
sha256.js
2120 ms
md5.min.js
2122 ms
swfobject.js
2163 ms
dialog.css
2177 ms
reset.css
2373 ms
tabloid.css
2843 ms
items.css
2667 ms
util.css
2429 ms
tistory-grid-min.css
2772 ms
items.js
2581 ms
menubar.css
2606 ms
628 ms
brand
39 ms
brand
51 ms
functions.js
2506 ms
lightbox.min.js
2609 ms
roosevelt_dk_bt.js
881 ms
webfont.js
5 ms
analytics.js
19 ms
durlBasic.css
227 ms
durlEventListner.js
711 ms
linkid.js
32 ms
collect
5 ms
collect
65 ms
check.php
299 ms
265AC03856A9F2581611CD
2204 ms
233E004E55EC1EE9163E4D
4294 ms
getpr.php
126 ms
tab_top.gif
715 ms
271D133E549E79DD1A9E93
1289 ms
25280C3653A8386E11B32A
1682 ms
266AD43653A8386E1C7A29
1604 ms
%EB%B0%B1%EB%AF%B8%EB%9F%AC%EB%B0%B0%EB%84%88_%EB%84%A4%EC%9D%B4%EB%B2%84.jpg
2370 ms
em12.png
952 ms
dnsever-banner_170x35.gif
510 ms
2236293D56DC0B77311F0F
1665 ms
23689D3A5675419B1BDB70
2048 ms
2347A73656FD19E002F307
1607 ms
2231A53E56EE3AAA076A0F
1912 ms
21106735563F1DED2678D1
1838 ms
26179B395610E164169FC9
1626 ms
2505C74C5688F36B180F3E
1464 ms
23417F36567E1F7103E4A7
1270 ms
201B8B3F50BDE3CC1A3E14
1589 ms
2236293D56DC0B77311F0F
1431 ms
2740F83F56F770DE35488F
2114 ms
2720FC3857051E0D1633A0
1880 ms
267DD64656FD166E291A07
1659 ms
2740F83F56F770DE35488F
1897 ms
2720FC3857051E0D1633A0
1674 ms
2142054E547126F1094583
1903 ms
227D963D538344C623EFB6
1673 ms
close.png
291 ms
loading.gif
291 ms
prev.png
292 ms
next.png
290 ms
2153D64B565C44B911F537
1741 ms
2478F53856D0F19233F76D
1635 ms
2123254A549E510C12A21C
1633 ms
22456734544BAF411AB596
1679 ms
13301A48513E00F138BA23
1313 ms
2261814556C81E6638D508
1635 ms
242DC43856DCF5600DC44F
1823 ms
emblem_006.gif
738 ms
234F8E50551FE8520131A9
1607 ms
new_ico_2.gif
704 ms
tab_closed.gif
704 ms
navi_back_active.gif
707 ms
tab_treed.gif
707 ms
tab_treed_end.gif
707 ms
tab_isleaf.gif
709 ms
img_emblem01.gif
710 ms
emblem_edition.png
710 ms
emblem_all.png
714 ms
2014_badge.png
713 ms
2013_badge.png
713 ms
2012_badge.png
960 ms
2011_badge.png
721 ms
2010_best.png
720 ms
2009_best.png
721 ms
2463294E55A4FE6F23C118
2225 ms
gtm.js
106 ms
all.js
24 ms
bgBoxTop.gif
270 ms
bgBox.gif
263 ms
mainImage.jpg
769 ms
100_.jpg
1727 ms
bgBoxLine2.gif
516 ms
iconNotice2.gif
519 ms
counterTotal.gif
502 ms
barCategory.gif
520 ms
google_custom_search_watermark.gif
83 ms
tnm_badge_white.gif
480 ms
286 ms
barRecentComment.gif
688 ms
bgBoxBottom.gif
705 ms
bgBoxBottom1.gif
701 ms
tab_opened.gif
612 ms
2012_badge.png
613 ms
03.gif
627 ms
xd_arbiter.php
83 ms
xd_arbiter.php
100 ms
widget.json.js
505 ms
td.min.js
1447 ms
collect
57 ms
xd_arbiter.php
9 ms
widget.adsense.js
541 ms
NMR
479 ms
NMR
481 ms
NMR
504 ms
footer_tnm.gif
472 ms
statistics.tattermedia.com
513 ms
TPMN_ad.php
503 ms
footsteps
1931 ms
loader.js
15528 ms
jquery.min.js
20 ms
client.js
237 ms
standardbanner.html
715 ms
standardbanner.css
276 ms
jquery.word-break-keep-all.edited.min.js
525 ms
connector.js
527 ms
builder.js
546 ms
adInformation.tpmn
566 ms
banner.html
921 ms
banner.js
296 ms
ajs.php
33 ms
100mirror.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.
100mirror.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
100mirror.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 100mirror.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 100mirror.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.
100mirror.com
Open Graph data is detected on the main page of 100 Mirror. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: