8.8 sec in total
1.2 sec
5.6 sec
2 sec
Visit criarloja.pt now to see the best up-to-date Criarloja content for Portugal and also check out these interesting facts you probably never knew about criarloja.pt
Criar uma Loja Online agora é facil. Abra a sua Loja Online desde 19,90 EUR MÊS
Visit criarloja.ptWe analyzed Criarloja.pt page load time and found that the first response time was 1.2 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
criarloja.pt performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value3.8 s
54/100
25%
Value5.7 s
52/100
10%
Value520 ms
56/100
30%
Value0
100/100
15%
Value6.0 s
64/100
10%
1183 ms
60 ms
72 ms
84 ms
50 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 50% of them (80 requests) were addressed to the original Criarloja.pt, 23% (36 requests) were made to Google.com and 8% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Criarloja.pt.
Page size can be reduced by 1.9 MB (40%)
4.7 MB
2.8 MB
In fact, the total size of Criarloja.pt main page is 4.7 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. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 36.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. This page needs HTML code to be minified as it can gain 7.0 kB, which is 15% 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 36.2 kB or 80% of the original size.
Potential reduce by 510.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, Criarloja needs image optimization as it can save up to 510.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.3 MB
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 1.3 MB or 77% of the original size.
Potential reduce by 91.8 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. Criarloja.pt needs all CSS files to be minified and compressed as it can save up to 91.8 kB or 83% of the original size.
Number of requests can be reduced by 60 (40%)
149
89
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Criarloja. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
criarloja.pt
1183 ms
css
60 ms
css
72 ms
css
84 ms
js
50 ms
normalize.css
201 ms
pricingtable.css
217 ms
index.css
219 ms
screen.css
217 ms
mobile-reset.css
221 ms
mobile.css
221 ms
jQuery.Opie.PortfolioGallery.css
396 ms
component.css
416 ms
pcss3t.css
418 ms
jquery-1.9.1.js
731 ms
jquery-migrate-1.2.1.min.js
416 ms
jquery-ui.js
759 ms
jQuery.easing.min.js
595 ms
jQuery.Opie.PortfolioGallery.min.js
612 ms
classie.js
615 ms
modernizr.custom.js
613 ms
jquery.sequence-min.js
798 ms
jquery.slider.min.js
811 ms
cbpScroller.js
818 ms
niceScroll.js
927 ms
jquery.counters.min.js
926 ms
framework.js
941 ms
css-pricing-tables.css
992 ms
hover.js
1014 ms
init.js
1017 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
54 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
63 ms
maps
47 ms
mask-pixel.png
191 ms
logo3.png
200 ms
call.png
202 ms
bg.jpg
342 ms
dot_inactive.png
263 ms
browser.png
1263 ms
arrow1.png
390 ms
arrow2.png
398 ms
arrow3.png
399 ms
mbl-browser.png
663 ms
browser1.png
539 ms
bg2.png
591 ms
triangle.png
597 ms
triangle-reverse.png
601 ms
feat06.png
752 ms
feat03.png
788 ms
feat01.png
802 ms
feat00.png
811 ms
feat02.png
863 ms
feat2.png
954 ms
feat3.png
987 ms
feat4.png
1000 ms
1.png
1207 ms
ex2.png
1238 ms
ex3.png
1450 ms
ex4.png
1478 ms
ex5.png
1401 ms
ex6.png
1584 ms
ex7.png
1744 ms
ex8.png
1730 ms
ex9.png
1921 ms
ex10.png
1878 ms
ex11.png
1898 ms
css
29 ms
font-awesome.css
1753 ms
embed
552 ms
ex12.png
1989 ms
ex13.png
2263 ms
ex14.png
2031 ms
ex15.png
2255 ms
ex16.png
2254 ms
ex17.png
2071 ms
ex18.png
2232 ms
ex19.png
2141 ms
ex20.png
2177 ms
ex21.png
2318 ms
backoffice.png
615 ms
loja.png
732 ms
js
86 ms
init_embed.js
68 ms
map_twitter.png
1990 ms
map_facebook.png
2034 ms
mb.png
2088 ms
help.png
956 ms
no.png
973 ms
yes.png
979 ms
location.png
1515 ms
atrk.js
89 ms
analytics.js
44 ms
common.js
61 ms
map.js
88 ms
google4.png
120 ms
overlay.js
56 ms
util.js
114 ms
onion.js
111 ms
search_impl.js
111 ms
collect
86 ms
atrk.gif
117 ms
stats.js
76 ms
openhand_8_8.cur
56 ms
test.png
332 ms
ViewportInfoService.GetViewportInfo
210 ms
controls.js
158 ms
widget_v2.132.js
12 ms
__$$__stringtable_lang_pt.js
13 ms
transparent.png
42 ms
css
36 ms
entity11.png
127 ms
mapcnt6.png
60 ms
vt
152 ms
vt
160 ms
vt
124 ms
vt
126 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
71 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
98 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
98 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
96 ms
vt
125 ms
vt
130 ms
vt
172 ms
vt
169 ms
vt
174 ms
vt
166 ms
vt
178 ms
vt
211 ms
vt
221 ms
vt
225 ms
vt
228 ms
vt
214 ms
vt
227 ms
vt
264 ms
vt
274 ms
vt
255 ms
vt
264 ms
vt
274 ms
vt
285 ms
vt
292 ms
vt
303 ms
vt
315 ms
vt
313 ms
vt
291 ms
vt
308 ms
vt
825 ms
vt
823 ms
vt
814 ms
vt
821 ms
vt
825 ms
vt
824 ms
tmapctrl.png
60 ms
ViewportInfoService.GetViewportInfo
56 ms
kh
89 ms
kh
101 ms
avatar_simple_visitor.png
116 ms
dot_active.png
103 ms
aL63HcygAAVYuCCsAAA==
7 ms
AuthenticationService.Authenticate
13 ms
criarloja.pt accessibility score
criarloja.pt 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
criarloja.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Criarloja.pt 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 Portuguese. Our system also found out that Criarloja.pt 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.
criarloja.pt
Open Graph description is not detected on the main page of Criarloja. 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: