3.3 sec in total
315 ms
2.4 sec
580 ms
Click here to check amazing Rich Count content. Otherwise, check out these important facts you probably never knew about richcount.com
라치카운트에서 할인정보/할인코드/프로모션 정보를 찾아보세요! 여행/숙박/호텔/엑티비티/항공권/티켓/자유이용권 등 다양한 할인정보를 얻어보세요!
Visit richcount.comWe analyzed Richcount.com page load time and found that the first response time was 315 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
richcount.com performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value4.2 s
45/100
25%
Value3.0 s
94/100
10%
Value160 ms
93/100
30%
Value0.01
100/100
15%
Value5.4 s
72/100
10%
315 ms
26 ms
108 ms
135 ms
138 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 47% of them (47 requests) were addressed to the original Richcount.com, 18% (18 requests) were made to Maps.google.com and 9% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (989 ms) belongs to the original domain Richcount.com.
Page size can be reduced by 822.1 kB (23%)
3.6 MB
2.7 MB
In fact, the total size of Richcount.com main page is 3.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. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 25.0 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 8.4 kB, which is 28% 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 25.0 kB or 83% of the original size.
Potential reduce by 181.5 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. Rich Count images are well optimized though.
Potential reduce by 478.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 478.1 kB or 69% of the original size.
Potential reduce by 137.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. Richcount.com needs all CSS files to be minified and compressed as it can save up to 137.6 kB or 83% of the original size.
Number of requests can be reduced by 32 (36%)
88
56
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rich Count. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
richcount.com
315 ms
css
26 ms
bootstrap.min.css
108 ms
font-awesome.min.css
135 ms
misc.css
138 ms
style.css
142 ms
responsive-320.css
140 ms
responsive-360.css
165 ms
responsive-ipad.css
181 ms
richcount-logo.jpg
233 ms
google_map_gen.js
319 ms
google_map_gen.js
325 ms
jquery-1.10.2.min.js
261 ms
jquery.singlePageNav.js
221 ms
jquery.flexslider.js
223 ms
jquery.prettyPhoto.js
260 ms
custom.js
259 ms
us-flag1.png
306 ms
uk-flag1.png
304 ms
aus-flag1.png
298 ms
ind-flag1.png
299 ms
Events.png
361 ms
banner1a.jpg
500 ms
banner4.jpg
667 ms
banner1.jpg
437 ms
banner5.jpg
706 ms
banner6.jpg
718 ms
banner3.jpg
744 ms
Map_section_img.png
627 ms
Corporate_RC.png
669 ms
Management_RC.png
706 ms
Mission_RC.png
721 ms
Website-writing.png
793 ms
Technical-writing.png
799 ms
SEO-writing.png
793 ms
Travel-writing.png
815 ms
Newsletter-writing.png
813 ms
SEO-services.png
866 ms
Article-writing.png
989 ms
Blog-writing.png
987 ms
Press-release-writing.png
892 ms
goal.jpg
873 ms
Heat.jpg
874 ms
remax.jpg
885 ms
logo-neyox.png
872 ms
alexnova.jpg
864 ms
Ralph.jpg
842 ms
webace.jpg
796 ms
valley.jpg
795 ms
kpoc.jpg
884 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
5 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
10 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
11 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
17 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
16 ms
map.php
252 ms
map.php
247 ms
maps
30 ms
api
21 ms
gmlocalsearch.js
23 ms
gmlocalsearch.js
37 ms
default+en.I.js
10 ms
common.js
27 ms
map.js
28 ms
overlay.js
25 ms
util.js
24 ms
marker.js
22 ms
infowindow.js
17 ms
StaticMapService.GetMapImage
233 ms
onion.js
81 ms
css
37 ms
transparent.png
122 ms
ViewportInfoService.GetViewportInfo
107 ms
stats.js
104 ms
controls.js
99 ms
StaticMapService.GetMapImage
202 ms
mapcnt6.png
122 ms
js
201 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
174 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
172 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
173 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
173 ms
ViewportInfoService.GetViewportInfo
154 ms
google4.png
40 ms
marker.png
85 ms
vt
61 ms
vt
60 ms
vt
59 ms
vt
58 ms
vt
61 ms
vt
61 ms
vt
54 ms
tmapctrl.png
48 ms
cb_scout5.png
47 ms
tmapctrl4.png
47 ms
imgs8.png
47 ms
AuthenticationService.Authenticate
17 ms
vt
20 ms
AuthenticationService.Authenticate
16 ms
richcount.com accessibility score
richcount.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
Browser errors were logged to the console
richcount.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Richcount.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 Richcount.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.
richcount.com
Open Graph description is not detected on the main page of Rich Count. 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: