4.4 sec in total
482 ms
3.3 sec
574 ms
Welcome to locarise.com homepage info - get ready to check Locarise best content right away, or after learning these important things about locarise.com
Our solutions use advanced sensors and Wi-Fi marketing to boost your retail business.
Visit locarise.comWe analyzed Locarise.com page load time and found that the first response time was 482 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
locarise.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value9.4 s
0/100
25%
Value6.5 s
38/100
10%
Value200 ms
89/100
30%
Value0
100/100
15%
Value8.0 s
42/100
10%
482 ms
28 ms
423 ms
659 ms
508 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 11% of them (7 requests) were addressed to the original Locarise.com, 60% (38 requests) were made to D3m01b6ni7t3fn.cloudfront.net and 24% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source D3m01b6ni7t3fn.cloudfront.net.
Page size can be reduced by 1.3 MB (50%)
2.6 MB
1.3 MB
In fact, the total size of Locarise.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. 80% 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 69.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. 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 69.6 kB or 81% of the original size.
Potential reduce by 36.7 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. Locarise images are well optimized though.
Potential reduce by 386.2 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 386.2 kB or 71% of the original size.
Potential reduce by 791.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. Locarise.com needs all CSS files to be minified and compressed as it can save up to 791.4 kB or 89% of the original size.
Number of requests can be reduced by 33 (72%)
46
13
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Locarise. 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 13 to 1 for CSS and as a result speed up the page load time.
482 ms
webfont.js
28 ms
wp-emoji-release.min.js
423 ms
settings.css
659 ms
wordpress-svg-icon-plugin-style.min.css
508 ms
layout.css
368 ms
main.css
677 ms
shortcodes.css
800 ms
mediaelementplayer.min.css
439 ms
prettyPhoto.css
501 ms
style.css
525 ms
responsive.css
658 ms
jquery.js
736 ms
jquery-migrate.min.js
296 ms
jquery.themepunch.tools.min.js
960 ms
jquery.themepunch.revolution.min.js
1019 ms
svg-inline-min.js
811 ms
js
50 ms
css
31 ms
icons.css
804 ms
js_composer.css
1176 ms
brad-love.js
834 ms
wp-embed.min.js
176 ms
js_composer_front.js
850 ms
waypoints.min.js
850 ms
modernizr.js
987 ms
fitvids.min.js
996 ms
prettyPhoto.js
1006 ms
plugins.js
1159 ms
skrollr.js
1056 ms
imagesloaded.js
1140 ms
jquery.scrollTo.min.js
1151 ms
bxslider.min.js
1162 ms
main.min.js
1215 ms
comment-reply.min.js
307 ms
style.css
896 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
72 ms
IgZJs4-7SA1XX_edsoXWog.ttf
76 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
75 ms
k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf
78 ms
O4NhV7_qs9r9seTo7fnsVKCWcynf_cDxXwCLxiixG1c.ttf
77 ms
PRmiXeptR36kaC0GEAetxne1Pd76Vl7zRpE7NLJQ7XU.ttf
75 ms
ZKwULyCG95tk6mOqHQfRBC3USBnSvpkopQaUR-2r7iU.ttf
75 ms
do7-0avPC2vxor6SN2THGA.ttf
76 ms
Li18TEFObx_yGdzKDoI_ci3USBnSvpkopQaUR-2r7iU.ttf
76 ms
STBOO2waD2LpX45SXYjQBS3USBnSvpkopQaUR-2r7iU.ttf
69 ms
WmVKXVcOuffP_qmCpFuyzS3USBnSvpkopQaUR-2r7iU.ttf
72 ms
7dO2Hj7qB8nRVFK0svQqRqCWcynf_cDxXwCLxiixG1c.ttf
69 ms
lFxvRPuGFG5ktd7P0WRwKtqQynqKV_9Plp7mupa0S4g.ttf
68 ms
ZCcPJiCGOzh84o2siPk48V02b4v3fUxqf9CZJ1qUoIA.ttf
69 ms
5xAt7XK2vkUdjhGtt98uneGMkauwsY7KZ6tVtEZSDQ4.ttf
66 ms
fontAwesome.woff
673 ms
logo_locarise_inline.png
405 ms
logo_locarise_inline_white.png
221 ms
centralemb.jpg
223 ms
prods.jpg
619 ms
instore.jpg
406 ms
partners.jpg
404 ms
dashduphone.png
618 ms
tokyodashi.png
775 ms
shutterstock_35227632.jpg
705 ms
large_left.png
160 ms
large_right.png
161 ms
locarise.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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.
locarise.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
locarise.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Locarise.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Locarise.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.
locarise.com
Open Graph description is not detected on the main page of Locarise. 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: