17.1 sec in total
2.3 sec
14.5 sec
252 ms
Click here to check amazing Locus content for South Korea. Otherwise, check out these important facts you probably never knew about locus.com
Visit locus.comWe analyzed Locus.com page load time and found that the first response time was 2.3 sec and then it took 14.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
locus.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value41.6 s
0/100
25%
Value30.0 s
0/100
10%
Value1,320 ms
17/100
30%
Value0.797
5/100
15%
Value39.0 s
0/100
10%
2315 ms
408 ms
25 ms
406 ms
808 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 94% of them (48 requests) were addressed to the original Locus.com, 4% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Locus.com.
Page size can be reduced by 620.0 kB (24%)
2.6 MB
2.0 MB
In fact, the total size of Locus.com main page is 2.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. 20% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 37.3 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 37.3 kB or 83% of the original size.
Potential reduce by 11.8 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. Locus images are well optimized though.
Potential reduce by 145.8 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 145.8 kB or 67% of the original size.
Potential reduce by 425.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. Locus.com needs all CSS files to be minified and compressed as it can save up to 425.1 kB or 87% of the original size.
Number of requests can be reduced by 27 (57%)
47
20
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.locus.com
2315 ms
language-selector.css
408 ms
css
25 ms
style.css
406 ms
bbpress-mod.css
808 ms
wpml-mod.css
460 ms
grid.css
768 ms
base.css
991 ms
layout.css
1577 ms
shortcodes.css
2051 ms
magnific-popup.css
1014 ms
mediaelementplayer.css
1370 ms
enfold.css
2408 ms
custom.css
1458 ms
animate.min.css
2165 ms
style.css
1561 ms
jquery.js
2614 ms
jquery-migrate.min.js
1880 ms
jquery.gmap.min.js
1967 ms
avia-compat.js
2282 ms
editor.js
1998 ms
avia.js
4533 ms
shortcodes.js
3428 ms
jquery.magnific-popup.min.js
2624 ms
mediaelement-and-player.min.js
3296 ms
wp-mediaelement.js
2515 ms
comment-reply.min.js
2725 ms
public.min.js
2979 ms
sitepress.js
3142 ms
201408_logo3.jpg
1000 ms
ko.png
1119 ms
en.png
1297 ms
main_001.jpg
3997 ms
main_002.jpg
2823 ms
main_007.jpg
3332 ms
main_006.jpg
6606 ms
main_005.jpg
3606 ms
main_004.jpg
3991 ms
main_003.jpg
5318 ms
main_008.jpg
6204 ms
main_009.jpg
5912 ms
201509_002.jpg
4812 ms
172-300x300.jpg
4462 ms
2-013.jpg
5843 ms
172.jpg
5270 ms
201509_009-36x36.jpg
5796 ms
201509_010-36x36.jpg
5775 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
5 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
11 ms
entypo-fontello.woff
6540 ms
print.css
233 ms
locus.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
locus.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
General
Impact
Issue
Detected JavaScript libraries
locus.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locus.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Korean. Our system also found out that Locus.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.
locus.com
Open Graph description is not detected on the main page of Locus. 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: