4.7 sec in total
284 ms
4.1 sec
351 ms
Welcome to oboticario.pt homepage info - get ready to check Oboticario best content for Portugal right away, or after learning these important things about oboticario.pt
Descobre os nossos Perfumes, Maquilhagem, Cosméticos, Presentes e mais. Celebra o amor com presentes que emocionam.
Visit oboticario.ptWe analyzed Oboticario.pt page load time and found that the first response time was 284 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
oboticario.pt performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value7.1 s
6/100
25%
Value15.8 s
0/100
10%
Value7,170 ms
0/100
30%
Value0.603
10/100
15%
Value25.2 s
0/100
10%
284 ms
618 ms
138 ms
258 ms
431 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 80% of them (94 requests) were addressed to the original Oboticario.pt, 3% (4 requests) were made to Google-analytics.com and 3% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Oboticario.pt.
Page size can be reduced by 971.3 kB (26%)
3.8 MB
2.8 MB
In fact, the total size of Oboticario.pt main page is 3.8 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 87.5 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 87.5 kB or 78% of the original size.
Potential reduce by 69.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. Oboticario images are well optimized though.
Potential reduce by 622.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 622.1 kB or 69% of the original size.
Potential reduce by 191.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. Oboticario.pt needs all CSS files to be minified and compressed as it can save up to 191.8 kB or 87% of the original size.
Number of requests can be reduced by 55 (49%)
113
58
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oboticario. 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 11 to 1 for CSS and as a result speed up the page load time.
oboticario.pt
284 ms
618 ms
fbevents.js
138 ms
stylesheet.css
258 ms
geral_boticario.css
431 ms
style.php
414 ms
jquery.fancybox-1.3.4.css
270 ms
style.css
630 ms
jquery-ui-1.8.20.custom.css
426 ms
jquery-ui-1.8.15.custom.css
447 ms
facebox.css
392 ms
rateit.css
484 ms
jquery-1.8.3.min.js
855 ms
innovaeditor.js
511 ms
jquery-ui-1.8.14.custom.min.js
641 ms
jquery-ui-1.8.20.custom.min.js
622 ms
jquery.cycle.all.js
664 ms
jquery.fancybox-1.3.4.pack.js
679 ms
facebox.js
710 ms
javascript.php
735 ms
jquery.rateit.js
717 ms
jquery.swipe.js
755 ms
jquery.jscroll.min.js
764 ms
scripts.js
729 ms
addthis_widget.js
17 ms
ptcd00692c3bfe59267d5ecfac5310286c.js
277 ms
103 ms
121 ms
istoolbar.css
95 ms
istoolbar.js
93 ms
editor.js
429 ms
editor_lang.js
93 ms
label_novidade-roxo.png
110 ms
8630112_210.jpg
108 ms
8585361_210.jpg
107 ms
8585348_210.jpg
107 ms
8604764_210.jpg
238 ms
logo-boticario-topo-768.png
108 ms
banner-pricipal-ameixa_promo-especial-pt_41834022956d03a9b3b8fd.png
522 ms
banner-pricipal-perfumaria-pt_53721170956c4632ae2c59.png
962 ms
banner-pricipal-top-nativa-spa-pt_104621610456c4579fe45ca.png
805 ms
banner-pricipal-boleto-pt_187222250156c4583535e47.png
820 ms
banner-pequeno-active-pt_155475487556c458cf951e4.png
371 ms
banner-pequeno-iscas-pt_120730780756c45902cf85f.png
489 ms
banner-pequeno-novidades-pt_176028653956c45930aa9f5.png
554 ms
banner-pequeno-24h-pt_94000746656c4595dd8d4d.png
669 ms
banner-medio-top-nativa-spa-pt_98232366656c45a05ef6ce.png
615 ms
banner-medio-perfumaria-pt_152336085356c45a3f0213e.png
741 ms
8585249_270.jpg
703 ms
8585348_270.jpg
758 ms
8621145_270.jpg
789 ms
8630115_230.jpg
833 ms
8624642_230.jpg
848 ms
8630112_230.jpg
876 ms
bannerfundacao_12793426152a06af6e8f23.png
905 ms
logo-paypal-footer.jpg
908 ms
logo-mastercard-footer.jpg
925 ms
logo-visa-footer.jpg
936 ms
logo-securedby-footer.jpg
961 ms
opentag-103446-1356189.js
22 ms
all.js
200 ms
bg-header.jpg
991 ms
icon-facebook21px_147195245b1768e102.png
974 ms
icon-twitter21px_100845245b1b0039b6.png
994 ms
icon-youtube21px_262425245b1c9d08c8.png
1002 ms
icon-flickr21px_290755245b1f87eb7e.png
1021 ms
icon-googleplus21px_66015245b22056863.png
1024 ms
bg-newsletter-topo.png
1060 ms
separador-idioma.png
1062 ms
logo-boticario-topo.png
1085 ms
ga.js
52 ms
300lo.json
75 ms
bg-pesquisa-topo.png
1014 ms
icon-logintopo.png
1028 ms
icon-sacocompras-topo.png
1029 ms
bg-menu-topo.png
1069 ms
OpenSans-Italic-webfont.woff
1072 ms
sh.7c7179124ea24ac6ba46caac.html
61 ms
pct
196 ms
activity
181 ms
activity
189 ms
__utm.gif
43 ms
__utm.gif
25 ms
__utm.gif
28 ms
pixel
37 ms
pixel
23 ms
24 ms
OpenSans-LightItalic-webfont.woff
951 ms
match-result
5 ms
xd_arbiter.php
223 ms
xd_arbiter.php
429 ms
tag2
175 ms
OpenSans-SemiboldItalic-webfont.woff
843 ms
OpenSans-BoldItalic-webfont.woff
735 ms
OpenSans-ExtraBoldItalic-webfont.woff
707 ms
OpenSans-Regular-webfont.woff
713 ms
OpenSans-Light-webfont.woff
662 ms
OpenSans-Semibold-webfont.woff
638 ms
OpenSans-Bold-webfont.woff
598 ms
OpenSans-ExtraBold-webfont.woff
577 ms
bg-submenu.png
559 ms
bg-menu-topo-linhas.png
567 ms
mask-destaque-grande.png
557 ms
mask-banner230.png
573 ms
mask-banner480.png
560 ms
icon-disponivel-small.png
544 ms
icon-sacocompras-btn.png
519 ms
separador-menuFooter.jpg
539 ms
seta-menuFooter.png
541 ms
icon-facebook30px_272945245b1768d271.png
554 ms
icon-youtube30px_281095245b1c9cfebc.png
542 ms
icon-flickr30px_209265245b1e85a762.png
527 ms
icon-googleplus30px_219685245b2204c9bd.png
520 ms
delete.gif
541 ms
star.png
547 ms
bullets-paginacao-destaqueGrande.png
543 ms
print.css
93 ms
oboticario.pt accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
oboticario.pt 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
Browser errors were logged to the console
Page has valid source maps
oboticario.pt 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
Tap targets are not sized appropriately
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oboticario.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Oboticario.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.
oboticario.pt
Open Graph description is not detected on the main page of Oboticario. 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: