4.3 sec in total
689 ms
3.2 sec
364 ms
Visit alannam.com now to see the best up-to-date Alannam content and also check out these interesting facts you probably never knew about alannam.com
app官网下载安装公司拥有一支自主创新的设计研发团队,app官网下载安装在这里你可以享受到更好的体验
Visit alannam.comWe analyzed Alannam.com page load time and found that the first response time was 689 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
alannam.com performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value2.6 s
87/100
25%
Value5.4 s
56/100
10%
Value30 ms
100/100
30%
Value0.128
82/100
15%
Value2.3 s
99/100
10%
689 ms
221 ms
8 ms
284 ms
216 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Alannam.com, 33% (39 requests) were made to Blogimgs.naver.net and 22% (26 requests) were made to Blogimgs.naver.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 1.1 MB (69%)
1.6 MB
505.1 kB
In fact, the total size of Alannam.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 400 B
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 400 B or 46% of the original size.
Potential reduce by 27.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. Obviously, Alannam needs image optimization as it can save up to 27.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 822.9 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 822.9 kB or 74% of the original size.
Potential reduce by 248.1 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. Alannam.com needs all CSS files to be minified and compressed as it can save up to 248.1 kB or 86% of the original size.
Number of requests can be reduced by 67 (56%)
119
52
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alannam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
alannam.com
689 ms
alann
221 ms
Frameset-981964519.js
8 ms
PrologueList.nhn
284 ms
NBlogHidden.nhn
216 ms
Hidden-597428542.js
5 ms
MusicPlayer-449972894.js
13 ms
LayoutTopCommon-484882993.css
9 ms
player-846d457.css
18 ms
RemoveSubDomain-dea9950.js
20 ms
Jindo152-363950062.js
22 ms
LayoutTopCommon-730083628.js
32 ms
JindoComponent-318925938.js
32 ms
PrologueWebzine-71207160.css
32 ms
gnb_quirks_euckr.nhn
79 ms
allowSwfForChrome-7dd9772.js
68 ms
LayoutBottomCommon-902441421.js
68 ms
0005_body.gif
169 ms
spc.gif
151 ms
PrologueList.nhn
320 ms
%BB%E7%BA%BB_-b.jpg
159 ms
btn_confirm2.gif
144 ms
%EA%B7%B8%EB%A6%BC1.jpg
162 ms
0006_login.png
173 ms
btn_confirm.gif
144 ms
btn_cancel.gif
145 ms
btn_close.gif
147 ms
btn_thin_close.gif
147 ms
btn_close8.gif
154 ms
ico_file.gif
154 ms
btn_download2.gif
154 ms
btn_cancel3.gif
156 ms
btn_close3.gif
154 ms
btn_close5.gif
156 ms
btn_confirm.gif
157 ms
btn_cancel.gif
158 ms
btn_close_1.gif
157 ms
btn_viewexif.gif
159 ms
btn_originaldn.gif
160 ms
spc.gif
162 ms
tit_viewexif.gif
161 ms
ico_notice2.gif
161 ms
btn_close.gif
162 ms
btn_close3.gif
163 ms
btn_close.gif
163 ms
btn_ok.gif
163 ms
btn_close2.gif
164 ms
btn_confirm_pop2.gif
164 ms
btn_cancel_pop2.gif
165 ms
ico_help.gif
138 ms
attachImage_3473150802.jpeg
469 ms
attachImage_275835947.jpeg
447 ms
attachImage_499239224.jpeg
493 ms
attachImage_3382209822.jpeg
508 ms
attachImage_3871697480.jpeg
445 ms
attachImage_2596843986.jpeg
501 ms
attachImage_173297140.jpeg
857 ms
attachImage_3172706308.jpeg
1139 ms
attachImage_4259852265.jpeg
930 ms
IMG_0350.JPG
1077 ms
8614.jpg
1081 ms
NaverBlog_20140204_123909_00.jpg
1090 ms
UAN_7739.jpg
1383 ms
%B1%D7%B8%B213.png
1594 ms
iPhone_0.jpg
1634 ms
promo_npay.png
140 ms
3334.jpg
725 ms
WidgetView.nhn
224 ms
WidgetListAsync.nhn
353 ms
m
462 ms
btn_blogsearch.gif
46 ms
bg_library.jpg
44 ms
lib_h.gif
44 ms
sp_widget_lib.png
47 ms
shadow.png
47 ms
shadow02.png
46 ms
bg_not_available_word.gif
49 ms
0156_773.gif
95 ms
0126_back1.gif
37 ms
0126_back2.gif
37 ms
0126_back3.gif
42 ms
0126_back4.gif
41 ms
0126_back6.gif
41 ms
0126_back7.gif
44 ms
0126_back8.gif
44 ms
0126_back9.gif
44 ms
0151_head.gif
52 ms
0151_body.gif
50 ms
0151_footer.gif
50 ms
0101_image.gif
43 ms
0118_back.gif
44 ms
exchange01_1.gif
45 ms
exchange01_2.gif
44 ms
section_connect_widget-2fd595e.css
3 ms
jindo.min-78c07e0.js
8 ms
agent.ie11-6694cec.js
17 ms
BuddyConnectWidget-242001126.js
16 ms
bg_skin9.gif
21 ms
%B1%D7%B8%B21.jpg
37 ms
b.gif
19 ms
login_basic.gif
7 ms
Winter+Leaves.jpg
28 ms
imagesCA5CQTYQ.jpg
40 ms
profileImage.jpg
31 ms
4.png
55 ms
b.gif
9 ms
ico_arr2.gif
10 ms
btn_skin9_addn.gif
5 ms
btn_skin9_admin.png
7 ms
btn_skin9_download.png
6 ms
btn_skin9_help.png
8 ms
%B1%D7%B8%B21.jpg
37 ms
2726390.gif
503 ms
0149_head.gif
26 ms
sp_widget_map_v4.png
16 ms
bg_country_v3.gif
14 ms
0149_body.gif
29 ms
0149_icon.gif
26 ms
0149_footer.gif
30 ms
getLoginStatus.nhn
406 ms
alannam.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
alannam.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
Page has valid source maps
alannam.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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alannam.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Alannam.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.
alannam.com
Open Graph description is not detected on the main page of Alannam. 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: