Etpsico.Pt etpsico.pt

Intra.Etpsico.Pt

intra.etpsico.pt receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank intra.etpsico.pt is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in Leiria, Leiria, 2400-822, Portugal and links to network IP address 212.13.43.214. This server doesn't support HTTPS and doesn't support HTTP/2.

About - intra.etpsico.pt


Technologies used on Website

Web Servers
IIS
Web Frameworks
Microsoft ASP.NET
Operating Systems
Windows Server

intra.etpsico.pt Profile

Title: :::::---GestProf---::::
Description: Ministra cursos técnicos de Informática/Gestão, Automação Industrial, Planeamento e Gestão da Produção, Desenhador Projectista e Química Tecnológica/Analista de Laboratório. Descrição da escola, serviços prestados e notícias actualizadas. Alvaiázere, Avelar(Ansião) e Penela
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with etpsico.pt in any way. Only publicly available statistics data are displayed.

How popular is intra.etpsico.pt?

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Unique Visitors:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  intra.etpsico.pt
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is intra.etpsico.pt?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
etpsico.pt
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
etpsico.pt
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much intra.etpsico.pt can earn?

Daily Revenue:
n/a
Monthly Revenue:
n/a
Yearly Revenue:
n/a
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do intra.etpsico.pt lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is intra.etpsico.pt worth?

Website Value:
n/a

+ Where is intra.etpsico.pt hosted?

Server IP:
212.13.43.214
ASN:
AS12305 
ISP:
G9Telecom S.A. 
Server Location:
Leiria
Leiria, 10
2400-822
Portugal, PT
 

Other sites hosted on 212.13.43.214

There are no other sites hosted on this IP

+ How fast does intra.etpsico.pt load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Serve images in next-gen formats - Potential savings of 33 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://intra.etpsico.pt/image/imgent.jpg
37 KB18 KB
http://intra.etpsico.pt/image/youtube.jpg
20 KB15 KB
Avoids an excessive DOM size - 107 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
107
Maximum DOM Depth
8
Maximum Child Elements
9
Keep request counts low and transfer sizes small - 14 requests • 120 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
14120 KB
Image
8110 KB
Stylesheet
14 KB
Script
43 KB
Document
13 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 260 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://intra.etpsico.pt/fich_css/f1.css
4 KB70
http://intra.etpsico.pt/FICH_js/nao_botao_dir.js
1 KB110
http://intra.etpsico.pt/FICH_js/msg_barra_status.js
1 KB110
http://intra.etpsico.pt/FICH_js/top.js
1 KB110
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://intra.etpsico.pt/
0 ms131 ms3 KB7 KB200text/htmlDocument
http://intra.etpsico.pt/fich_css/f1.css
146 ms278 ms4 KB73 KB200text/cssStylesheet
http://intra.etpsico.pt/FICH_js/nao_botao_dir.js
146 ms271 ms1 KB1 KB200application/javascriptScript
http://intra.etpsico.pt/FICH_js/msg_barra_status.js
147 ms280 ms1 KB1 KB200application/javascriptScript
http://intra.etpsico.pt/FICH_js/top.js
148 ms279 ms1 KB1 KB200application/javascriptScript
http://intra.etpsico.pt/image/globo.jpg
148 ms288 ms8 KB8 KB200image/jpegImage
http://intra.etpsico.pt/image/imgent.jpg
148 ms325 ms38 KB37 KB200image/jpegImage
http://intra.etpsico.pt/image/livros.jpg
287 ms561 ms27 KB27 KB200image/jpegImage
http://intra.etpsico.pt/FICH_js/bemvindo_rodape.js
286 ms412 ms1 KB0 KB200application/javascriptScript
http://intra.etpsico.pt/image/Rodape_pagina_web.png
148 ms336 ms0 KB0 KB-1Image
http://intra.etpsico.pt/image/facebook.gif
287 ms414 ms2 KB2 KB200image/gifImage
http://intra.etpsico.pt/image/instagram.jpg
287 ms464 ms7 KB7 KB200image/jpegImage
http://intra.etpsico.pt/image/twitter_logo_header.png
288 ms427 ms7 KB7 KB200image/pngImage
http://intra.etpsico.pt/image/youtube.jpg
288 ms455 ms21 KB20 KB200image/jpegImage
Serve static assets with an efficient cache policy - 12 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://intra.etpsico.pt/image/imgent.jpg
0 ms38 KB
http://intra.etpsico.pt/image/livros.jpg
0 ms27 KB
http://intra.etpsico.pt/image/youtube.jpg
0 ms21 KB
http://intra.etpsico.pt/image/globo.jpg
0 ms8 KB
http://intra.etpsico.pt/image/instagram.jpg
0 ms7 KB
http://intra.etpsico.pt/image/twitter_logo_header.png
0 ms7 KB
http://intra.etpsico.pt/fich_css/f1.css
0 ms4 KB
http://intra.etpsico.pt/image/facebook.gif
0 ms2 KB
http://intra.etpsico.pt/FICH_js/top.js
0 ms1 KB
http://intra.etpsico.pt/FICH_js/msg_barra_status.js
0 ms1 KB
http://intra.etpsico.pt/FICH_js/nao_botao_dir.js
0 ms1 KB
http://intra.etpsico.pt/FICH_js/bemvindo_rodape.js
0 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
164 ms
8 ms
319 ms
47 ms
370 ms
7 ms
447 ms
23 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
120 ms3 ms1 ms
Properly size images - Potential savings of 77 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://intra.etpsico.pt/image/livros.jpg
27 KB26 KB
http://intra.etpsico.pt/image/imgent.jpg
37 KB21 KB
http://intra.etpsico.pt/image/youtube.jpg
20 KB20 KB
http://intra.etpsico.pt/image/instagram.jpg
7 KB6 KB
http://intra.etpsico.pt/image/twitter_logo_header.png
7 KB4 KB
Avoids enormous network payloads - Total size was 120 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://intra.etpsico.pt/image/imgent.jpg
38 KB
http://intra.etpsico.pt/image/livros.jpg
27 KB
http://intra.etpsico.pt/image/youtube.jpg
21 KB
http://intra.etpsico.pt/image/globo.jpg
8 KB
http://intra.etpsico.pt/image/instagram.jpg
7 KB
http://intra.etpsico.pt/image/twitter_logo_header.png
7 KB
http://intra.etpsico.pt/fich_css/f1.css
4 KB
http://intra.etpsico.pt/
3 KB
http://intra.etpsico.pt/image/facebook.gif
2 KB
http://intra.etpsico.pt/FICH_js/top.js
1 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
65 ms
Other
29 ms
Rendering
13 ms
Script Evaluation
11 ms
Parse HTML & CSS
8 ms
Script Parsing & Compilation
8 ms
Avoid chaining critical requests - 5 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 130 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 2205 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Properly size images - Potential savings of 44 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://intra.etpsico.pt/image/livros.jpg
27 KB20 KB
http://intra.etpsico.pt/image/youtube.jpg
20 KB18 KB
http://intra.etpsico.pt/image/instagram.jpg
7 KB6 KB
Avoids enormous network payloads - Total size was 180 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://intra.etpsico.pt/image/Rodape_pagina_web.png
60 KB
http://intra.etpsico.pt/image/imgent.jpg
38 KB
http://intra.etpsico.pt/image/livros.jpg
27 KB
http://intra.etpsico.pt/image/youtube.jpg
21 KB
http://intra.etpsico.pt/image/globo.jpg
8 KB
http://intra.etpsico.pt/image/instagram.jpg
7 KB
http://intra.etpsico.pt/image/twitter_logo_header.png
7 KB
http://intra.etpsico.pt/fich_css/f1.css
4 KB
http://intra.etpsico.pt/
3 KB
http://intra.etpsico.pt/image/facebook.gif
2 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
132 ms
Other
117 ms
Script Evaluation
38 ms
Rendering
32 ms
Parse HTML & CSS
29 ms
Script Parsing & Compilation
25 ms
Garbage Collection
2 ms
Serve images in next-gen formats - Potential savings of 70 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://intra.etpsico.pt/image/Rodape_pagina_web.png
59 KB38 KB
http://intra.etpsico.pt/image/imgent.jpg
37 KB18 KB
http://intra.etpsico.pt/image/youtube.jpg
20 KB15 KB
Avoids an excessive DOM size - 107 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
107
Maximum DOM Depth
8
Maximum Child Elements
9
Keep request counts low and transfer sizes small - 14 requests • 180 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
14180 KB
Image
8169 KB
Stylesheet
14 KB
Script
43 KB
Document
13 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 670 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://intra.etpsico.pt/fich_css/f1.css
4 KB180
http://intra.etpsico.pt/FICH_js/nao_botao_dir.js
1 KB330
http://intra.etpsico.pt/FICH_js/msg_barra_status.js
1 KB330
http://intra.etpsico.pt/FICH_js/top.js
1 KB330
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://intra.etpsico.pt/
0 ms273 ms3 KB7 KB200text/htmlDocument
http://intra.etpsico.pt/fich_css/f1.css
286 ms715 ms4 KB73 KB200text/cssStylesheet
http://intra.etpsico.pt/FICH_js/nao_botao_dir.js
286 ms678 ms1 KB1 KB200application/javascriptScript
http://intra.etpsico.pt/FICH_js/msg_barra_status.js
286 ms420 ms1 KB1 KB200application/javascriptScript
http://intra.etpsico.pt/FICH_js/top.js
286 ms549 ms1 KB1 KB200application/javascriptScript
http://intra.etpsico.pt/image/globo.jpg
287 ms560 ms8 KB8 KB200image/jpegImage
http://intra.etpsico.pt/image/imgent.jpg
287 ms780 ms38 KB37 KB200image/jpegImage
http://intra.etpsico.pt/image/livros.jpg
687 ms948 ms27 KB27 KB200image/jpegImage
http://intra.etpsico.pt/FICH_js/bemvindo_rodape.js
561 ms686 ms1 KB0 KB200application/javascriptScript
http://intra.etpsico.pt/image/Rodape_pagina_web.png
722 ms1023 ms60 KB59 KB200image/pngImage
http://intra.etpsico.pt/image/facebook.gif
722 ms851 ms2 KB2 KB200image/gifImage
http://intra.etpsico.pt/image/instagram.jpg
722 ms863 ms7 KB7 KB200image/jpegImage
http://intra.etpsico.pt/image/twitter_logo_header.png
722 ms986 ms7 KB7 KB200image/pngImage
http://intra.etpsico.pt/image/youtube.jpg
722 ms973 ms21 KB20 KB200image/jpegImage
Serve static assets with an efficient cache policy - 13 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://intra.etpsico.pt/image/Rodape_pagina_web.png
0 ms60 KB
http://intra.etpsico.pt/image/imgent.jpg
0 ms38 KB
http://intra.etpsico.pt/image/livros.jpg
0 ms27 KB
http://intra.etpsico.pt/image/youtube.jpg
0 ms21 KB
http://intra.etpsico.pt/image/globo.jpg
0 ms8 KB
http://intra.etpsico.pt/image/instagram.jpg
0 ms7 KB
http://intra.etpsico.pt/image/twitter_logo_header.png
0 ms7 KB
http://intra.etpsico.pt/fich_css/f1.css
0 ms4 KB
http://intra.etpsico.pt/image/facebook.gif
0 ms2 KB
http://intra.etpsico.pt/FICH_js/top.js
0 ms1 KB
http://intra.etpsico.pt/FICH_js/msg_barra_status.js
0 ms1 KB
http://intra.etpsico.pt/FICH_js/nao_botao_dir.js
0 ms1 KB
http://intra.etpsico.pt/FICH_js/bemvindo_rodape.js
0 ms1 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
300 ms
8 ms
747 ms
24 ms
775 ms
13 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
325 ms9 ms4 ms
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 5 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 270 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use 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.

Dados AVZ and 2 others render only 5 pixels tall (14 CSS pixels) .
Para aceder, clique na imagem and 5 others render only 4 pixels tall (11 CSS pixels) .
inclui Sistema…da Qualidade) renders only 5 pixels tall (12 CSS pixels) .
Copyright © 20…/ E.T.P. Sicó renders only 5 pixels tall (14 CSS pixels) .
Escola Tecnoló…sional de Sicó renders only 5 pixels tall (13 CSS pixels) .
Site otimizado…ção 1024x768 ( and 2 others render only 4 pixels tall (10 CSS pixels) .
I.E. renders only 4 pixels tall (10 CSS pixels) .

Configure 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.

Configure a viewport for this page.

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:

http://intra.etpsico.pt/FICH_js/bemvindo_rodape.js (expiration not specified)
http://intra.etpsico.pt/FICH_js/msg_barra_status.js (expiration not specified)
http://intra.etpsico.pt/FICH_js/nao_botao_dir.js (expiration not specified)
http://intra.etpsico.pt/FICH_js/top.js (expiration not specified)
http://intra.etpsico.pt/fich_css/f1.css (expiration not specified)
http://intra.etpsico.pt/image/Rodape_pagina_web.png (expiration not specified)
http://intra.etpsico.pt/image/facebook.gif (expiration not specified)
http://intra.etpsico.pt/image/globo.jpg (expiration not specified)
http://intra.etpsico.pt/image/imgent.jpg (expiration not specified)
http://intra.etpsico.pt/image/instagram.jpg (expiration not specified)
http://intra.etpsico.pt/image/livros.jpg (expiration not specified)
http://intra.etpsico.pt/image/twitter_logo_header.png (expiration not specified)
http://intra.etpsico.pt/image/youtube.jpg (expiration not specified)

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 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.Optimize CSS Delivery of the following:

http://intra.etpsico.pt/fich_css/f1.css

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 73KiB (47% reduction).

Compressing and resizing http://intra.etpsico.pt/image/livros.jpg could save 24.8KiB (92% reduction).
Compressing and resizing http://intra.etpsico.pt/image/youtube.jpg could save 18.8KiB (92% reduction).
Compressing http://intra.etpsico.pt/image/Rodape_pagina_web.png could save 15.4KiB (26% reduction).
Compressing http://intra.etpsico.pt/image/imgent.jpg could save 6.7KiB (19% reduction).
Compressing and resizing http://intra.etpsico.pt/image/instagram.jpg could save 5.9KiB (89% reduction).
Compressing http://intra.etpsico.pt/image/globo.jpg could save 1.3KiB (17% reduction).

Size 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,452 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <hr class="um"> falls outside the viewport.
The element <hr class="um"> falls outside the viewport.
The element <hr class="um"> falls outside the viewport.

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.

The tap target <a href="http://www.etpsico.pt" class="tresxinin">Escola Tecnoló…sional de Sicó</a> is close to 1 other tap targets .
The tap target <a href="http://instagram.com/etp_sico"></a> is close to 2 other tap targets .

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 848B (20% reduction).

Minifying http://intra.etpsico.pt/fich_css/f1.css could save 848B (20% reduction) after compression.

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 p*** times.

Minify HTML for the following resources to reduce their size by 609B (29% reduction).

Minifying http://intra.etpsico.pt/ could save 609B (29% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does intra.etpsico.pt use compression?

intra.etpsico.pt use gzip compression.
Original size: 6.95 KB
Compressed size: 2.54 KB
File reduced by: 4.41 KB (63%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

intra.etpsico.pt does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

intra.etpsico.pt does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Centro/Educação

+ Http Header

Cache-Control: private
Content-Type: text/html
Content-Encoding: gzip
Vary: Accept-Encoding
Server: Microsoft-IIS/10.0
Set-Cookie: ASPSESSIONIDCCCCDBCR=ILIJJLICHMHKICEKLBGHDKJA; path=/
X-Powered-By: ASP.NET
X-UA-Compatible: IE=EmulateIE9
Date: Sat, 09 Nov 2019 09:55:03 GMT
Content-Length: 2602

+ DNS Lookup

Type Ip Target TTL
A 212.13.43.214 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

Currently Not Available
Last update was 4 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with etpsico.pt in any way. Only publicly available statistics data are displayed.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
intra.etpsico.pt widget