5 sec in total
581 ms
4.1 sec
316 ms
Click here to check amazing IStore content for Portugal. Otherwise, check out these important facts you probably never knew about istore.pt
A loja iStore é uma a APR - Apple Premium Reseller - e comercializa produtos Apple e acessórios relacionados.
Visit istore.ptWe analyzed Istore.pt page load time and found that the first response time was 581 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
istore.pt performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value15.5 s
0/100
25%
Value15.1 s
1/100
10%
Value2,870 ms
3/100
30%
Value1.244
1/100
15%
Value32.5 s
0/100
10%
581 ms
299 ms
312 ms
316 ms
61 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 59% of them (41 requests) were addressed to the original Istore.pt, 23% (16 requests) were made to Gallery.mbmkt.info and 7% (5 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Gallery.mbmkt.info.
Page size can be reduced by 687.9 kB (45%)
1.5 MB
838.0 kB
In fact, the total size of Istore.pt main page is 1.5 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 55.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 16.7 kB, which is 27% 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 55.0 kB or 89% of the original size.
Potential reduce by 351.3 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, IStore needs image optimization as it can save up to 351.3 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 157.5 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 157.5 kB or 74% of the original size.
Potential reduce by 124.2 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. Istore.pt needs all CSS files to be minified and compressed as it can save up to 124.2 kB or 88% of the original size.
Number of requests can be reduced by 21 (33%)
63
42
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IStore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
istore.pt
581 ms
main.css
299 ms
home.css
312 ms
responsive.css
316 ms
jquery.min.js
61 ms
main.js
316 ms
dropkick.css
1290 ms
dropkick.min.js
1448 ms
dropkick.jquery.js
466 ms
jquery.nicescroll.js
515 ms
jquery.cycle2.min.js
467 ms
jquery.cycle2.tile.min.js
466 ms
jcarousellite_1.0.1.min.js
514 ms
jquery.fancybox-1.3.4.css
510 ms
jquery.fancybox-1.3.4.pack.js
510 ms
jquery.etalage.min.js
569 ms
jquery.cookie.js
575 ms
jquery-ui.css
38 ms
jquery.ui.widget.js
60 ms
jquery.ui.mouse.js
63 ms
jquery.ui.slider.js
66 ms
contact.js
576 ms
css
29 ms
cart_icon.png
109 ms
Site-AppleWatch.jpg
2141 ms
logo.png
499 ms
search_icon.png
292 ms
arrow_down.png
304 ms
slide_shadow2.png
306 ms
left_white_icon.png
385 ms
right_white_icon.png
399 ms
slide_shadow_left.png
401 ms
slide_shadow_right.png
478 ms
white_carbon.png
494 ms
offer_icon.png
971 ms
link.png
570 ms
loading.gif
590 ms
cart.png
589 ms
bg_dotted.png
663 ms
payment.png
968 ms
accordain_icon.png
779 ms
footer_sep.png
756 ms
arrow.png
850 ms
microphone.png
864 ms
so_twitter.png
937 ms
so_face.png
959 ms
iStore_Mac_10_Q216_iS_SM_1457638778.jpg
2197 ms
iS_iPad_Air_2_20x_Q2_16_SM_1457452750.jpg
2114 ms
Site-Beats.jpg
2067 ms
iS_Madeirashopping_Site_iS_SM-5.jpg
3173 ms
iS_Apple_Watch_Brevemente_iS_SM-_2.jpg
3085 ms
iStore_inmove_carbon_out_15_SM_4.jpg
2352 ms
thumb.php
2198 ms
thumb.php
2210 ms
thumb.php
2289 ms
thumb.php
2381 ms
thumb.php
2305 ms
thumb.php
2383 ms
thumb.php
2400 ms
thumb.php
2449 ms
1.png
2472 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
7 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
45 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
44 ms
URSgP3aplSko3CQAzdXHwPesZW2xOQ-xsNqO47m55DA.ttf
45 ms
analytics.js
94 ms
header_cart.php
113 ms
arrow_right.png
96 ms
collect
13 ms
istore.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
[role]s do not have all required [aria-*] attributes
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.
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.
istore.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
istore.pt 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Istore.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Istore.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.
istore.pt
Open Graph description is not detected on the main page of IStore. 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: