shifter.pt website information.
shifter.pt domain name is registered by .PT top-level domain registry. See the other sites registred in .PT domain zone.
Following name servers are specified for shifter.pt domain:
- ns2.pointerns.com
- ns1.pointerns.com
and probably website shifter.pt is hosted by AMAZON-02 - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-02 - Amazon.com, Inc., US hosting company.
According to Alexa traffic rank the highest website shifter.pt position was 57479 (in the world). The lowest Alexa rank position was 979692. Now website shifter.pt ranked in Alexa database as number 740570 (in the world).
Website shifter.pt Desktop speed measurement score (74/100) is better than the results of 57.94% of other sites shows that the page desktop performance can be improved.
shifter.pt Mobile usability score (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of shifter.pt (47/100) is better than the results of 28.68% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
Date | Rank | Change |
---|---|---|
Nov-28-2024 | 740,570 | -15,733 |
Nov-27-2024 | 724,837 | -21,958 |
Nov-26-2024 | 702,879 | 36,135 |
Nov-25-2024 | 739,014 | 13,213 |
Nov-24-2024 | 752,227 | -25,676 |
Nov-23-2024 | 726,551 | 10,258 |
Nov-22-2024 | 736,809 | -22,213 |
Advertisement
shifter.pt Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
shifter.pt whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
shifter.pt server information
shifter.pt desktop page speed rank
Last tested: 2019-06-14
shifter.pt Desktop Speed Test Quick Summary
priority - 16 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 41 blocking script resources and 17 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://shifter.sapo.pt/wp-includes/js/jquery/jque…grate.min.js?ver=1.4.1
https://shifter.sapo.pt/wp-content/plugins/wordpre…4.2.0.min.js?ver=4.2.2
https://www.googletagmanager.com/gtag/js?id=UA-28098602-3
https://www.googletagmanager.com/gtag/js?id=UA-34456715-44
https://use.fontawesome.com/39a4eb633c.js
https://cdnjs.cloudflare.com/ajax/libs/notify/0.4.2/notify.js
https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/1.5.10/clipboard.min.js
https://shifter.sapo.pt/wp-content/plugins/disqus-…nt_count.js?ver=3.0.17
https://shifter.sapo.pt/wp-content/plugins/instagr…tagram.min.js?ver=1.12
https://s0.wp.com/wp-content/js/devicepx-jetpack.js?ver=201924
https://shifter.sapo.pt/wp-content/plugins/quantca…cript.min.js?ver=1.2.2
https://shifter.sapo.pt/wp-content/plugins/quantca…async.min.js?ver=1.2.2
https://shifter.sapo.pt/wp-content/themes/presso/i…nt-search.js?ver=3.2.1
https://shifter.sapo.pt/wp-content/themes/presso/j…othScroll.js?ver=1.4.6
https://shifter.sapo.pt/wp-content/themes/presso/j…verIntent.js?ver=1.8.1
https://shifter.sapo.pt/wp-content/themes/presso/j…y.fitvids.js?ver=1.1.0
https://shifter.sapo.pt/wp-content/themes/presso/j…crollbar.js?ver=0.6.13
https://shifter.sapo.pt/wp-includes/js/imagesloaded.min.js?ver=3.2.0
https://shifter.sapo.pt/wp-content/themes/presso/j….pkgd.min.js?ver=3.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j….pkgd.min.js?ver=2.0.0
https://shifter.sapo.pt/wp-content/themes/presso/j…mpatibility.js?ver=1.3
https://shifter.sapo.pt/wp-content/themes/presso/j…fic-popup.js?ver=1.1.0
https://shifter.sapo.pt/wp-content/themes/presso/j…superfish.js?ver=1.7.9
https://shifter.sapo.pt/wp-content/themes/presso/j…y-sidebar.js?ver=1.5.0
https://shifter.sapo.pt/wp-content/themes/presso/j…waypoints.js?ver=4.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ts/inview.js?ver=4.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ts/sticky.js?ver=4.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ick/slick.js?ver=1.6.0
https://shifter.sapo.pt/wp-includes/js/jquery/ui/effect.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/e…fade.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/core.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/a…dion.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/tabs.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-content/themes/presso/js/shortcodes.js?ver=3.2.1
https://shifter.sapo.pt/wp-content/plugins/newslet…/validate.js?ver=6.0.7
https://shifter.sapo.pt/wp-content/themes/presso-child/js/main.js?ver=3.2.1
https://shifter.sapo.pt/wp-includes/js/wp-embed.min.js?ver=5.2.1
https://js.sapo.pt/Projects/CPU/latest/lazypub.min.js
https://shifter.sapo.pt/wp-content/themes/presso-child/js/mixitup.min.js
Optimize CSS Delivery of the following:
https://shifter.sapo.pt/wp-content/plugins/instagr…agram.min.css?ver=1.12
https://shifter.sapo.pt/wp-content/plugins/quantca…tyle.min.css?ver=1.2.2
https://shifter.sapo.pt/wp-content/plugins/wordpre…/css/wpp.css?ver=4.2.2
https://shifter.sapo.pt/wp-content/themes/presso/f…s/zocial.css?ver=5.2.1
https://shifter.sapo.pt/wp-content/themes/presso/f…s/entypo.css?ver=5.2.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ck/slick.css?ver=5.2.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ck-theme.css?ver=5.2.1
https://shifter.sapo.pt/wp-content/themes/presso/style.css?ver=3.2.1
https://shifter.sapo.pt/wp-content/themes/presso-child/style.css?ver=3.2.1
https://fonts.googleapis.com/css?family=Libre+Baskerville:400,700
https://shifter.sapo.pt/wp-content/plugins/newsletter/style.css?ver=6.0.7
https://fonts.googleapis.com/css?family=Libre+Fran…0italic&ver=1537266877
https://shifter.sapo.pt/wp-content/plugins/jetpack/css/jetpack.css?ver=7.4
https://use.fontawesome.com/39a4eb633c.css
https://use.fontawesome.com/releases/v4.7.0/css/font-awesome-css.min.css
https://fonts.googleapis.com/css?family=Libre+Fran…700i,800,800i,900,900i
priority - 7 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 67.6KiB (46% reduction).
Compressing and resizing https://shifter.sapo.pt/wp-content/uploads/2018/03…2709134825-450x202.png could save 25.8KiB (68% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2019/06…er-um-meme-335x186.jpg could save 3.1KiB (12% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/11/Iniative-Q-335x186.jpg could save 907B (11% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2019/06…560430436156-90x60.jpg could save 405B (13% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2019/06…b162724f1f_b-90x60.jpg could save 383B (15% reduction).
priority - 5 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://shifterpt.disqus.com/count.js (5 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-28098602-3 (15 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-34456715-44 (15 minutes)
https://js.sapo.pt/Projects/bsuv3/js/bsuv3.min.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://js.sapo.pt/Projects/CPU/latest/lazypub.min.js (6 hours)
https://js.sapo.pt/Projects/bsuv3/img/logo.png (6 hours)
https://js.sapo.pt/Projects/bsuv3/img/new-02.png (6 hours)
https://z.moatads.com/sapoappnexusdisplay309000670041/moatad.js (6.4 hours)
priority - 3 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 29.2KiB (33% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…fic-popup.js?ver=1.1.0 could save 3.9KiB (33% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ick/slick.js?ver=1.6.0 could save 3.5KiB (26% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…othScroll.js?ver=1.4.6 could save 2.6KiB (42% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso-child/js/main.js?ver=3.2.1 could save 2KiB (27% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…y-sidebar.js?ver=1.5.0 could save 1.6KiB (47% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…verIntent.js?ver=1.8.1 could save 1.5KiB (66% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…crollbar.js?ver=0.6.13 could save 1.4KiB (16% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…waypoints.js?ver=4.0.1 could save 624B (18% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…superfish.js?ver=1.7.9 could save 507B (21% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…y.fitvids.js?ver=1.1.0 could save 426B (33% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ts/inview.js?ver=4.0.1 could save 251B (30% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-includes/js/jquery/ui/e…fade.min.js?ver=1.11.4 could save 228B (45% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ts/sticky.js?ver=4.0.1 could save 224B (32% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/newslet…/validate.js?ver=6.0.7 could save 214B (20% reduction).
Minifying https://shifter.sapo.pt/wp-content/plugins/quantca…async.min.js?ver=1.2.2 could save 202B (21% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…mpatibility.js?ver=1.3 could save 192B (49% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/disqus-…nt_count.js?ver=3.0.17 could save 184B (21% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/i…nt-search.js?ver=3.2.1 could save 145B (13% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/js/shortcodes.js?ver=3.2.1 could save 138B (22% reduction) after compression.
priority - 2 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 1 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 11.5KiB (24% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/f…s/entypo.css?ver=5.2.1 could save 1.3KiB (36% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso-child/style.css?ver=3.2.1 could save 987B (24% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/f…s/zocial.css?ver=5.2.1 could save 794B (40% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/newsletter/style.css?ver=6.0.7 could save 343B (29% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/wordpre…/css/wpp.css?ver=4.2.2 could save 307B (57% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ck-theme.css?ver=5.2.1 could save 247B (19% reduction) after compression.
Minifying https://use.fontawesome.com/39a4eb633c.css could save 134B (37% reduction) after compression.
priority - 1 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 7.2KiB (24% reduction).
Minifying https://static.quantcast.mgr.consensu.org/v18/cmp-3pc-check.html could save 159B (28% reduction).
priority - 0 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 1.6KiB (52% reduction).
Compressing https://shifter.sapo.pt/wp-content/plugins/disqus-…nt_count.js?ver=3.0.17 could save 449B (50% reduction).
Compressing https://static.quantcast.mgr.consensu.org/v18/cmp-3pc-check.html could save 266B (46% reduction).
Compressing https://shifter.sapo.pt/wp-includes/js/jquery/ui/e…fade.min.js?ver=1.11.4 could save 177B (35% reduction).
shifter.pt Desktop Resources
Total Resources | 142 |
Number of Hosts | 29 |
Static Resources | 109 |
JavaScript Resources | 53 |
CSS Resources | 18 |
shifter.pt Desktop Resource Breakdown
shifter.pt mobile page speed rank
Last tested: 2018-11-05
shifter.pt Mobile Speed Test Quick Summary
priority - 64 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 40 blocking script resources and 16 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
https://shifter.sapo.pt/wp-includes/js/jquery/jquery.js?ver=1.12.4
https://shifter.sapo.pt/wp-includes/js/jquery/jque…grate.min.js?ver=1.4.1
https://shifter.sapo.pt/wp-content/plugins/wordpre…4.2.0.min.js?ver=4.2.0
https://www.googletagmanager.com/gtag/js?id=UA-28098602-3
https://www.googletagmanager.com/gtag/js?id=UA-34456715-44
https://use.fontawesome.com/39a4eb633c.js
https://cdnjs.cloudflare.com/ajax/libs/notify/0.4.2/notify.js
https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/1.5.10/clipboard.min.js
https://shifter.sapo.pt/wp-content/plugins/disqus-…nt_count.js?ver=3.0.16
https://shifter.sapo.pt/wp-content/plugins/instagr…gram.min.js?ver=1.10.1
https://s0.wp.com/wp-content/js/devicepx-jetpack.js?ver=201845
https://shifter.sapo.pt/wp-content/themes/presso/i…nt-search.js?ver=3.2.1
https://shifter.sapo.pt/wp-content/themes/presso/j…othScroll.js?ver=1.4.6
https://shifter.sapo.pt/wp-content/themes/presso/j…verIntent.js?ver=1.8.1
https://shifter.sapo.pt/wp-content/themes/presso/j…y.fitvids.js?ver=1.1.0
https://shifter.sapo.pt/wp-content/themes/presso/j…crollbar.js?ver=0.6.13
https://shifter.sapo.pt/wp-includes/js/imagesloaded.min.js?ver=3.2.0
https://shifter.sapo.pt/wp-content/themes/presso/j….pkgd.min.js?ver=3.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j….pkgd.min.js?ver=2.0.0
https://shifter.sapo.pt/wp-content/themes/presso/j…mpatibility.js?ver=1.3
https://shifter.sapo.pt/wp-content/themes/presso/j…fic-popup.js?ver=1.1.0
https://shifter.sapo.pt/wp-content/themes/presso/j…superfish.js?ver=1.7.9
https://shifter.sapo.pt/wp-content/themes/presso/j…y-sidebar.js?ver=1.5.0
https://shifter.sapo.pt/wp-content/themes/presso/j…waypoints.js?ver=4.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ts/inview.js?ver=4.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ts/sticky.js?ver=4.0.1
https://shifter.sapo.pt/wp-content/themes/presso/j…ick/slick.js?ver=1.6.0
https://shifter.sapo.pt/wp-includes/js/jquery/ui/effect.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/e…fade.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/core.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/a…dion.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-includes/js/jquery/ui/tabs.min.js?ver=1.11.4
https://shifter.sapo.pt/wp-content/themes/presso/js/shortcodes.js?ver=3.2.1
https://shifter.sapo.pt/wp-content/plugins/newslet…/validate.js?ver=5.7.3
https://shifter.sapo.pt/wp-content/themes/presso-child/js/main.js?ver=3.2.1
https://shifter.sapo.pt/wp-includes/js/wp-embed.min.js?ver=4.9.8
https://js.sapo.pt/Projects/CPU/latest/lazypub.min.js
https://shifter.sapo.pt/wp-content/themes/presso-child/js/mixitup.min.js
Optimize CSS Delivery of the following:
https://shifter.sapo.pt/wp-content/plugins/instagr…ram.min.css?ver=1.10.1
https://shifter.sapo.pt/wp-content/plugins/wordpre…/css/wpp.css?ver=4.2.0
https://shifter.sapo.pt/wp-content/themes/presso/f…s/zocial.css?ver=4.9.8
https://shifter.sapo.pt/wp-content/themes/presso/f…s/entypo.css?ver=4.9.8
https://shifter.sapo.pt/wp-content/themes/presso/j…ck/slick.css?ver=4.9.8
https://shifter.sapo.pt/wp-content/themes/presso/j…ck-theme.css?ver=4.9.8
https://shifter.sapo.pt/wp-content/themes/presso/style.css?ver=3.2.1
https://shifter.sapo.pt/wp-content/themes/presso-child/style.css?ver=3.2.1
https://fonts.googleapis.com/css?family=Libre+Baskerville:400,700
https://shifter.sapo.pt/wp-content/plugins/newsletter/style.css?ver=5.7.3
https://fonts.googleapis.com/css?family=Libre+Fran…0italic&ver=1537266877
https://shifter.sapo.pt/wp-content/plugins/jetpack…/jetpack.css?ver=6.6.1
https://use.fontawesome.com/39a4eb633c.css
https://use.fontawesome.com/releases/v4.7.0/css/font-awesome-css.min.css
https://fonts.googleapis.com/css?family=Libre+Fran…700i,800,800i,900,900i
priority - 24 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 236.4KiB (40% reduction).
Compressing https://insite-sites.s3.amazonaws.com/IO-668f16a6/…Fotolia_66067004_X.jpg could save 32.2KiB (26% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/11…de-publica-335x223.png could save 18.2KiB (20% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/11…de-publica-335x186.png could save 15.5KiB (20% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2016/01…collier_02-768x512.jpg could save 12.3KiB (23% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2015/02…ybarradopt-800x534.jpg could save 9.6KiB (16% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/11/Iniative-Q-335x207.jpg could save 930B (11% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/11/Iniative-Q-335x186.jpg could save 907B (11% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/10…al-NASA_01-335x186.jpg could save 843B (24% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/05/PORTISHEAD-335x224.jpg could save 794B (16% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/11…jo-1-copia-335x186.jpg could save 760B (22% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/10…r-Gosto_01-335x186.jpg could save 757B (18% reduction).
Compressing https://shifter.sapo.pt/wp-content/uploads/2018/10…8-Porto_01-335x186.jpg could save 694B (11% reduction).
priority - 13 Reduce server response time
In our test, your server responded in 0.27 seconds.
There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 8 Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 7 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://insite-sites.s3.amazonaws.com/IO-ba657429/…5zLC3i4nds_unnamed.png (expiration not specified)
https://s3.amazonaws.com/insite-sites/_scripts/jquery.js (2 minutes)
https://s3.amazonaws.com/insite-sites/_scripts/popup.js (2 minutes)
https://s3.amazonaws.com/insite-sites/s-IO-ba657429/io-script.js?ver=1 (2 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-28098602-3 (15 minutes)
https://www.googletagmanager.com/gtag/js?id=UA-34456715-44 (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://js.sapo.pt/Projects/CPU/latest/lazypub.min.js (6 hours)
https://js.sapo.pt/Projects/bsuv3/js/bsuv3.min.js (6 hours)
priority - 3 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 29KiB (33% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…fic-popup.js?ver=1.1.0 could save 3.9KiB (33% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ick/slick.js?ver=1.6.0 could save 3.5KiB (26% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…othScroll.js?ver=1.4.6 could save 2.6KiB (42% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso-child/js/main.js?ver=3.2.1 could save 2KiB (27% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…y-sidebar.js?ver=1.5.0 could save 1.6KiB (47% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…verIntent.js?ver=1.8.1 could save 1.5KiB (66% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…crollbar.js?ver=0.6.13 could save 1.4KiB (16% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…waypoints.js?ver=4.0.1 could save 624B (18% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…superfish.js?ver=1.7.9 could save 507B (21% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…y.fitvids.js?ver=1.1.0 could save 426B (33% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ts/inview.js?ver=4.0.1 could save 251B (30% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-includes/js/jquery/ui/e…fade.min.js?ver=1.11.4 could save 228B (45% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ts/sticky.js?ver=4.0.1 could save 224B (32% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/newslet…/validate.js?ver=5.7.3 could save 214B (20% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…mpatibility.js?ver=1.3 could save 192B (49% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/disqus-…nt_count.js?ver=3.0.16 could save 184B (21% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/i…nt-search.js?ver=3.2.1 could save 145B (13% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/js/shortcodes.js?ver=3.2.1 could save 138B (22% reduction) after compression.
priority - 3 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 26.8KiB (83% reduction).
Compressing https://shifter.sapo.pt/wp-content/plugins/newslet…/validate.js?ver=5.7.3 could save 715B (65% reduction).
Compressing https://shifter.sapo.pt/wp-content/plugins/disqus-…nt_count.js?ver=3.0.16 could save 449B (50% reduction).
Compressing https://shifter.sapo.pt/wp-includes/js/jquery/ui/e…fade.min.js?ver=1.11.4 could save 177B (35% reduction).
priority - 2 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 15KiB (19% reduction).
Minifying https://insite.s3.amazonaws.com/io-editor/css/io-grid.css?ver=4.9.8 could save 3.4KiB (12% reduction).
Minifying https://shifter.sapo.pt/wp-content/themes/presso/f…s/entypo.css?ver=4.9.8 could save 1.3KiB (36% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso-child/style.css?ver=3.2.1 could save 987B (24% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/f…s/zocial.css?ver=4.9.8 could save 794B (40% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/newsletter/style.css?ver=5.7.3 could save 342B (29% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/plugins/wordpre…/css/wpp.css?ver=4.2.0 could save 307B (57% reduction) after compression.
Minifying https://shifter.sapo.pt/wp-content/themes/presso/j…ck-theme.css?ver=4.9.8 could save 247B (19% reduction) after compression.
Minifying https://use.fontawesome.com/39a4eb633c.css could save 134B (37% reduction) after compression.
priority - 1 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 8.9KiB (29% reduction).
shifter.pt Mobile Resources
Total Resources | 145 |
Number of Hosts | 24 |
Static Resources | 120 |
JavaScript Resources | 51 |
CSS Resources | 17 |
shifter.pt Mobile Resource Breakdown
shifter.pt mobile page usability
Last tested: 2018-11-05
shifter.pt Mobile Usability Test Quick Summary
priority - 5 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<button type="button" class="hamburger hamburger--spin"></button>
is close to 1 other tap targets.<a href="https://shifte…/joao-ribeiro/" class="vw-post-author__name">João Ribeiro</a>
is close to 1 other tap targets.The tap target
<a href="https://shifte…/arquitectura/" class="vw-cat-id-10639">Arquitectura</a>
and 85 others are close to other tap targets.The tap target
<a href="https://shifter.sapo.pt/web/" class="vw-cat-id-10 v…88 vw-cat-id-5">Web</a>
and 25 others are close to other tap targets.The tap target
<a href="https://shifte…calia-50-anos/" class="vw-post-box__link">A Tropicália e…fazem 50 anos</a>
and 1 others are close to other tap targets.The tap target
<a href="https://shifte…/pedro-arnaut/" class="vw-post-author__name">Pedro Arnaut</a>
and 1 others are close to other tap targets.The tap target
<div class="vw-side-panel__close-sub-menu">Back</div>
is close to 1 other tap targets.The tap target
<span class="vw-scroll-to-top"></span>
is close to 1 other tap targets.<div class="io-popup-close">
is close to 1 other tap targets.<a href="https://www.in…com/shifterpt/">
is close to 1 other tap targets.shifter.pt similar domains
www.shifter.net
www.shifter.org
www.shifter.info
www.shifter.biz
www.shifter.us
www.shifter.mobi
www.hifter.pt
www.shifter.pt
www.whifter.pt
www.swhifter.pt
www.wshifter.pt
www.ehifter.pt
www.sehifter.pt
www.eshifter.pt
www.dhifter.pt
www.sdhifter.pt
www.dshifter.pt
www.zhifter.pt
www.szhifter.pt
www.zshifter.pt
www.xhifter.pt
www.sxhifter.pt
www.xshifter.pt
www.ahifter.pt
www.sahifter.pt
www.ashifter.pt
www.sifter.pt
www.sbifter.pt
www.shbifter.pt
www.sbhifter.pt
www.sgifter.pt
www.shgifter.pt
www.sghifter.pt
www.syifter.pt
www.shyifter.pt
www.syhifter.pt
www.suifter.pt
www.shuifter.pt
www.suhifter.pt
www.sjifter.pt
www.shjifter.pt
www.sjhifter.pt
www.snifter.pt
www.shnifter.pt
www.snhifter.pt
www.shfter.pt
www.shufter.pt
www.shiufter.pt
www.shjfter.pt
www.shijfter.pt
www.shkfter.pt
www.shikfter.pt
www.shkifter.pt
www.shofter.pt
www.shiofter.pt
www.shoifter.pt
www.shiter.pt
www.shicter.pt
www.shifcter.pt
www.shicfter.pt
www.shidter.pt
www.shifdter.pt
www.shidfter.pt
www.shirter.pt
www.shifrter.pt
www.shirfter.pt
www.shitter.pt
www.shiftter.pt
www.shitfter.pt
www.shigter.pt
www.shifgter.pt
www.shigfter.pt
www.shivter.pt
www.shifvter.pt
www.shivfter.pt
www.shifer.pt
www.shifrer.pt
www.shiftrer.pt
www.shiffer.pt
www.shiftfer.pt
www.shiffter.pt
www.shifger.pt
www.shiftger.pt
www.shifyer.pt
www.shiftyer.pt
www.shifyter.pt
www.shiftr.pt
www.shiftwr.pt
www.shiftewr.pt
www.shiftwer.pt
www.shiftsr.pt
www.shiftesr.pt
www.shiftser.pt
www.shiftdr.pt
www.shiftedr.pt
www.shiftder.pt
www.shiftrr.pt
www.shifterr.pt
www.shifte.pt
www.shiftee.pt
www.shiftere.pt
www.shifteer.pt
www.shifted.pt
www.shifterd.pt
www.shiftef.pt
www.shifterf.pt
www.shiftefr.pt
www.shiftet.pt
www.shiftert.pt
www.shiftetr.pt
shifter.pt Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
shifter.pt TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.