sl.pt Website Information
Daily Unique Visits: 738
Daily Page Views: 1,476
Income Per Day: $5
Estimated Value: $1,200
This website is located in Portugal and is using following IP address 213.13.28.100. See the complete list of popular websites hosted in Portugal.
sl.pt is registered under .PT top-level domain. Please check other sites in .PT zone.
Website sl.pt is using the following name servers:
- dyndns-por01.ns.sapo.pt
- dyndns-lis01.ns.sapo.pt
and is probably hosted by MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA S.A.. See the full list of other websites hosted by MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA S.A..
The highest website sl.pt position in Alexa rank database was 15065 and the lowest rank position was 999291. Current position of sl.pt in Alexa rank database is 972057.
Desktop speed score of sl.pt (82/100) is better than the results of 74.03% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of sl.pt (60/100) is better than the results of 3.95% of other sites and means that the page is not mobile-friendly.
Mobile speed score of sl.pt (72/100) is better than the results of 79.79% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
sl.pt Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
sl.pt whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
sl.pt server information
Servers Location
sl.pt desktop page speed rank
Last tested: 2017-05-24
sl.pt Desktop Speed Test Quick Summary
priority - 6Enable 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 59.2KiB (80% reduction).
Compressing http://xsl.pt/rp/http_static/js/ajax.js could save 11.8KiB (77% reduction).
Compressing http://xsl.pt/ could save 10.6KiB (80% reduction).
Compressing http://imgs.sapo.pt/barimgs/bsu_apps_ntfs/AppBanners.js could save 7.5KiB (77% reduction).
Compressing http://xsl.pt/rp/http_static/js/puny.js could save 6.8KiB (76% reduction).
priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://js.sapo.pt/SAPO/
http://xsl.pt/rp/http_static/js/ajax.js
Optimize CSS Delivery of the following:
priority - 6Leverage 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:
http://xsl.pt/rp/http_static/images/bg.png (expiration not specified)
http://xsl.pt/rp/http_static/images/footer.png (expiration not specified)
http://xsl.pt/rp/http_static/images/header_bg.jpg (expiration not specified)
http://xsl.pt/rp/http_static/images/shadow_small.png (expiration not specified)
http://xsl.pt/rp/http_static/js/ajax.js (expiration not specified)
http://xsl.pt/rp/http_static/js/puny.js (expiration not specified)
http://assets.web.sapo.io/sapologos/current/b146b6…17b5e5bf313df7b184.png (15 minutes)
http://imgs.sapo.pt/barimgs/bsu_apps_ntfs/AppBanners.js (15 minutes)
http://assets.web.sapo.io/barimgs/bsu_v2.0/2.0.49/css/bsu.css?v=2.0.49 (60 minutes)
http://assets.web.sapo.io/barimgs/bsu_v2.0/2.0.49/img/sprite.png (60 minutes)
http://js.sapo.pt/SAPO/ (6 hours)
priority - 1Minify 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 7.7KiB (32% reduction).
Minifying http://xsl.pt/rp/http_static/js/puny.js could save 1.9KiB (22% reduction).
priority - 1Minify 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.3KiB (55% reduction).
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 620B (49% reduction).
sl.pt Desktop Resource Breakdown
Total Resources | 22 |
Number of Hosts | 8 |
Static Resources | 17 |
JavaScript Resources | 8 |
CSS Resources | 4 |
sl.pt mobile page speed rank
Last tested: 2018-06-15
sl.pt Mobile Speed Test Quick Summary
priority - 24Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://js.sapo.pt/SAPO/
http://xsl.pt/rp/http_static/js/ajax.js
Optimize CSS Delivery of the following:
priority - 8Leverage 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:
http://xsl.pt/rp/http_static/images/bg.png (expiration not specified)
http://xsl.pt/rp/http_static/images/footer.png (expiration not specified)
http://xsl.pt/rp/http_static/images/header_bg.jpg (expiration not specified)
http://xsl.pt/rp/http_static/images/shadow_small.png (expiration not specified)
http://xsl.pt/rp/http_static/js/ajax.js (expiration not specified)
http://xsl.pt/rp/http_static/js/puny.js (expiration not specified)
http://assets.web.sapo.io/sapologos/current/b146b6…17b5e5bf313df7b184.png (15 minutes)
http://imgs.sapo.pt/barimgs/bsu_apps_ntfs/AppBanners.js (15 minutes)
http://assets.web.sapo.io/barimgs/bsu_v2.0/2.0.53/css/bsu.css?v=2.0.53 (60 minutes)
http://assets.web.sapo.io/barimgs/bsu_v2.0/2.0.53/img/sprite2x.png (60 minutes)
http://js.sapo.pt/SAPO/ (6 hours)
priority - 5Enable 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 48.7KiB (79% reduction).
Compressing http://xsl.pt/rp/http_static/js/ajax.js could save 11.8KiB (77% reduction).
Compressing http://xsl.pt/ could save 7.6KiB (77% reduction).
Compressing http://xsl.pt/rp/http_static/js/puny.js could save 6.8KiB (76% reduction).
priority - 1Minify 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 7.7KiB (32% reduction).
Minifying http://xsl.pt/rp/http_static/js/puny.js could save 1.9KiB (22% reduction).
priority - 1Minify 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 5KiB (50% reduction).
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 620B (49% reduction).
sl.pt Mobile Resource Breakdown
Total Resources | 22 |
Number of Hosts | 8 |
Static Resources | 17 |
JavaScript Resources | 7 |
CSS Resources | 4 |
sl.pt mobile page usability
Last tested: 2018-06-15
sl.pt Mobile Usability Test Quick Summary
priority - 40Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Classificados
and 7 others render only 5 pixels tall (12 CSS pixels).Login
renders only 5 pixels tall (12 CSS pixels).Introduza uma…para comprimir
and 2 others render only 5 pixels tall (13 CSS pixels).Últimos Punys
and 1 others render only 7 pixels tall (19 CSS pixels).auto.sapo.pt/Carros/O…
and 5 others render only 5 pixels tall (14 CSS pixels).http://y0b.0p.xsl.pt
and 5 others render only 5 pixels tall (13 CSS pixels).Efectue o Login
renders only 7 pixels tall (19 CSS pixels).Permite-lhe:
renders only 5 pixels tall (13 CSS pixels).- Consultar es…dos seus punys
and 1 others render only 5 pixels tall (13 CSS pixels).login.sapo.pt
renders only 8 pixels tall (20 CSS pixels).PT
renders only 4 pixels tall (10 CSS pixels).|
renders only 4 pixels tall (10 CSS pixels).EN
renders only 4 pixels tall (10 CSS pixels).priority - 16Size 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.
<a id="bsu-v2-logo" href="http://www.sap…m_campaign=bsu">SAPO</a>
is close to 1 other tap targets.<a href="http://mail.sa…m_campaign=bsu" class="bsu-v2-link">Mail</a>
and 1 others are close to other tap targets.<a href="#vermais">Úteis</a>
is close to 1 other tap targets.<a id="bsu-v2-login" href="https://login.…2F%2Fxsl.pt%2F">Login</a>
is close to 1 other tap targets.<label for="public">Público</label>
and 1 others are close to other tap targets.<label for="public">Público</label>
and 3 others are close to other tap targets.<a href="http://auto.sa…t-2100778.aspx">auto.sapo.pt/Carros/O…</a>
and 5 others are close to other tap targets.<a href="http://y0b.0p.xsl.pt">http://y0b.0p.xsl.pt</a>
and 5 others are close to other tap targets.<a href="/?lang=pt" class="active">PT</a>
is close to 1 other tap targets.<a href="/?lang=en">EN</a>
is close to 1 other tap targets.priority - 10Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
priority - 3Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 1,010 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<div class="box_header">Efectue o Login</div>
falls outside the viewport.The element
<div class="siteWidth footer">PT | EN</div>
falls outside the viewport.sl.pt HTML validation
sl.pt similar domains
www.sl.net
www.sl.org
www.sl.info
www.sl.biz
www.sl.us
www.sl.mobi
www.l.pt
www.sl.pt
www.wl.pt
www.swl.pt
www.wsl.pt
www.el.pt
www.sel.pt
www.esl.pt
www.dl.pt
www.sdl.pt
www.dsl.pt
www.zl.pt
www.szl.pt
www.zsl.pt
www.xl.pt
www.sxl.pt
www.xsl.pt
www.al.pt
www.sal.pt
www.asl.pt
www.s.pt
www.sp.pt
www.slp.pt
www.spl.pt
www.so.pt
www.slo.pt
www.sol.pt
www.sk.pt
www.slk.pt
www.skl.pt
sl.pt Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
sl.pt TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.