Opolanco.Es - Info opolanco.es

opolanco.es receives about 119 unique visitors and 119 (1.00 per visitor) page views per day which should earn about $0.48/day from advertising revenue. Estimated site value is $231.99. According to Alexa Traffic Rank opolanco.es is ranked number 4,398,244 in the world and 7.0E-6% of global Internet users visit it. Site is hosted in Portugal and links to network IP address 217.76.150.74. This server doesn't support HTTPS and doesn't support HTTP/2.

About - opolanco.es


Technologies used on Website

Currently Not Available

opolanco.es Profile

Title: Hospital Obispo Polanco
Description: Información, publicaciones, boletín oncológico, actividades, comisiones, servicios y estadísticas del centro.
Last update was 34 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is opolanco.es?

119 daily visitors
Daily Unique Visitors:
119
Monthly Unique Visitors:
3,570
Pages per Visit:
1.00
Daily Pageviews:
119
Alexa Rank:
4,398,244 visit alexa
Alexa Reach:
7.0E-6%   (of global internet users)
Avg. visit duration:
01:19
Bounce rate:
90.00%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
16.51%
Referral:
68.37%
Search:
15.12%
Social:
0%
Paid:
0%

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  opolanco.es
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

On October 30 SEMrush is hosting first of a kind 24-hour online conference for marketers around the globe — Global Marketing Day. The event is designed for marketers to learn from the most successful in the field. Speakers from Google, Walt Disney, Adobe, BBC, WeWork, and many more will share real cases, tools and insights, so attendees can find out more about marketing in a day than many do by slaving over books for months. This unique experience is absolutely free!
Sign up & watch for free >>

+ Moz Data

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

+ How socially engaged is opolanco.es?

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:
opolanco.es
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:
opolanco.es
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 opolanco.es can earn?

Daily Revenue:
$0.48
Monthly Revenue:
$14.40
Yearly Revenue:
$175.20
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do opolanco.es 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 opolanco.es worth?

Website Value:
$231.99

+ Where is opolanco.es hosted?

Server IP:
217.76.150.74
ASN:
AS8560 
ISP:
1&1 Internet SE 
Server Location:

Portugal, PT
 

Other sites hosted on 217.76.150.74

+ How fast does opolanco.es load?

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

Page Speed (Google PageSpeed Insights) - Desktop

97
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

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.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 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.7 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 0.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 730 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://opolanco.es/css/reset.css
1 KB70
http://opolanco.es/css/general.css
19 KB190
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB150
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
4 KB110
http://opolanco.es/js/functions.js
3 KB110
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB310
http://opolanco.es/js/jquery/jquery-easing.js
4 KB70
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js
1 KB70
http://opolanco.es/js/jquery/jquery-plugin-wheel.js
1 KB70
Enable text compression - Potential savings of 121 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB83 KB
http://opolanco.es/css/general.css
19 KB16 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB9 KB
http://opolanco.es/
9 KB6 KB
http://opolanco.es/js/jquery/jquery-easing.js
4 KB3 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
3 KB2 KB
http://opolanco.es/js/functions.js
3 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://opolanco.es/
0 ms187 ms9 KB9 KB200text/htmlDocument
http://opolanco.es/css/reset.css
199 ms367 ms1 KB1 KB200text/cssStylesheet
http://opolanco.es/css/general.css
199 ms372 ms19 KB19 KB200text/cssStylesheet
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
199 ms367 ms13 KB13 KB200text/javascriptScript
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
199 ms362 ms4 KB3 KB200text/cssStylesheet
http://opolanco.es/js/functions.js
200 ms361 ms3 KB3 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-1.3.2.js
200 ms1077 ms118 KB118 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-easing.js
200 ms526 ms4 KB4 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js
200 ms525 ms1 KB1 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-plugin-wheel.js
200 ms543 ms1 KB1 KB200text/javascriptScript
http://opolanco.es/css/images/blank.gif
201 ms530 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/miga-pan.gif
201 ms954 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/home.gif
531 ms698 ms1 KB1 KB200image/gifImage
http://opolanco.es/css/images/arbol-dir.gif
699 ms861 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/correo.gif
862 ms1023 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/imprimir.gif
955 ms1132 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/miga-pan-verde.gif
1024 ms1184 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/mas-azul.gif
1101 ms1269 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/miga-pan-azul-claro.gif
1101 ms1266 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/guia-paciente2.gif
1101 ms1310 ms15 KB14 KB200image/gifImage
http://opolanco.es/css/images/bolsa-trabajo2.gif
1101 ms1426 ms15 KB15 KB200image/gifImage
http://opolanco.es/css/images/cea.gif
1101 ms1451 ms10 KB10 KB200image/gifImage
http://opolanco.es/css/images/urgencias2_1.gif
1102 ms1501 ms4 KB4 KB200image/gifImage
http://opolanco.es/css/images/urgencias2_2.gif
1102 ms1431 ms7 KB6 KB200image/gifImage
http://www.w3.org/Icons/valid-xhtml10-blue
1102 ms1278 ms2 KB2 KB200image/pngImage
http://jigsaw.w3.org/css-validator/images/vcss-blue
1102 ms1261 ms2 KB2 KB200image/gifImage
http://opolanco.es/css/images/itci.gif
1102 ms1436 ms1 KB1 KB200image/gifImage
http://opolanco.es/css/images/loveo.gif
1102 ms1473 ms1 KB1 KB200image/gifImage
http://www.google-analytics.com/ga.js
1102 ms1108 ms17 KB45 KB200text/javascriptScript
http://opolanco.es/css/images/baner.gif
1106 ms2067 ms48 KB47 KB200image/gifImage
http://opolanco.es/css/images/pestana-ini.gif
1106 ms1600 ms1 KB0 KB200image/gifImage
http://opolanco.es/css/images/pestana-med.gif
1107 ms1602 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/pestana-fin.gif
1108 ms1617 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/portada.gif
1108 ms1960 ms58 KB58 KB200image/gifImage
http://opolanco.es/css/images/barra-contenidos.gif
1108 ms1699 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/separador-verde.gif
1109 ms1762 ms2 KB2 KB200image/gifImage
http://opolanco.es/css/images/login.gif
1109 ms1769 ms3 KB2 KB200image/gifImage
http://opolanco.es/css/images/siguiente-gris.gif
1115 ms1783 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/pie.gif
1115 ms1869 ms1 KB1 KB200image/gifImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1011083970&utmhn=opolanco.es&utmcs=UTF-8&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Hospital%20Obispo%20Polanco&utmhid=1669207245&utmr=-&utmp=%2F&utmht=1568874746224&utmac=UA-16708699-1&utmcc=__utma%3D129689042.1141350130.1568874746.1568874746.1568874746.1%3B%2B__utmz%3D129689042.1568874746.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=1044667424&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
1187 ms1194 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 38 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://opolanco.es/js/jquery/jquery-1.3.2.js
0 ms118 KB
http://opolanco.es/css/images/portada.gif
0 ms58 KB
http://opolanco.es/css/images/baner.gif
0 ms48 KB
http://opolanco.es/css/general.css
0 ms19 KB
http://opolanco.es/css/images/bolsa-trabajo2.gif
0 ms15 KB
http://opolanco.es/css/images/guia-paciente2.gif
0 ms15 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
0 ms13 KB
http://opolanco.es/css/images/cea.gif
0 ms10 KB
http://opolanco.es/css/images/urgencias2_2.gif
0 ms7 KB
http://opolanco.es/css/images/urgencias2_1.gif
0 ms4 KB
http://opolanco.es/js/jquery/jquery-easing.js
0 ms4 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
0 ms4 KB
http://opolanco.es/js/functions.js
0 ms3 KB
http://opolanco.es/css/images/login.gif
0 ms3 KB
http://opolanco.es/css/images/separador-verde.gif
0 ms2 KB
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js
0 ms1 KB
http://opolanco.es/css/reset.css
0 ms1 KB
http://opolanco.es/css/images/pie.gif
0 ms1 KB
http://opolanco.es/css/images/home.gif
0 ms1 KB
http://opolanco.es/css/images/itci.gif
0 ms1 KB
http://opolanco.es/js/jquery/jquery-plugin-wheel.js
0 ms1 KB
http://opolanco.es/css/images/loveo.gif
0 ms1 KB
http://opolanco.es/css/images/pestana-ini.gif
0 ms1 KB
http://opolanco.es/css/images/pestana-med.gif
0 ms0 KB
http://opolanco.es/css/images/pestana-fin.gif
0 ms0 KB
http://opolanco.es/css/images/barra-contenidos.gif
0 ms0 KB
http://opolanco.es/css/images/miga-pan-azul-claro.gif
0 ms0 KB
http://opolanco.es/css/images/imprimir.gif
0 ms0 KB
http://opolanco.es/css/images/arbol-dir.gif
0 ms0 KB
http://opolanco.es/css/images/correo.gif
0 ms0 KB
http://opolanco.es/css/images/miga-pan.gif
0 ms0 KB
http://opolanco.es/css/images/miga-pan-verde.gif
0 ms0 KB
http://opolanco.es/css/images/mas-azul.gif
0 ms0 KB
http://opolanco.es/css/images/siguiente-gris.gif
0 ms0 KB
http://opolanco.es/css/images/blank.gif
0 ms0 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
http://jigsaw.w3.org/css-validator/images/vcss-blue
518400000 ms2 KB
http://www.w3.org/Icons/valid-xhtml10-blue
2592000000 ms2 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB27 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
215 ms
7 ms
224 ms
6 ms
1109 ms
15 ms
1126 ms
49 ms
1180 ms
6 ms
1186 ms
27 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
91 ms3 ms1 ms
http://opolanco.es/js/jquery/jquery-1.3.2.js
59 ms11 ms3 ms
Minify CSS - Potential savings of 6 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://opolanco.es/css/general.css
19 KB3 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
4 KB3 KB
Properly size images - Potential savings of 7 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://opolanco.es/css/images/cea.gif
10 KB7 KB
Remove unused CSS - Potential savings of 17 KB
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.

URL
SizePotential Savings
http://opolanco.es/css/general.css
19 KB13 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
4 KB4 KB
Avoids enormous network payloads - Total size was 366 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB
http://opolanco.es/css/images/portada.gif
58 KB
http://opolanco.es/css/images/baner.gif
48 KB
http://opolanco.es/css/general.css
19 KB
http://www.google-analytics.com/ga.js
17 KB
http://opolanco.es/css/images/bolsa-trabajo2.gif
15 KB
http://opolanco.es/css/images/guia-paciente2.gif
15 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB
http://opolanco.es/css/images/cea.gif
10 KB
http://opolanco.es/
9 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
55 ms
Style & Layout
46 ms
Script Evaluation
40 ms
Rendering
20 ms
Parse HTML & CSS
11 ms
Script Parsing & Compilation
7 ms
Avoids an excessive DOM size - 137 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
137
Maximum DOM Depth
11
Maximum Child Elements
9
Minify JavaScript - Potential savings of 51 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB47 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB5 KB
Keep request counts low and transfer sizes small - 40 requests • 366 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
40366 KB
Image
29175 KB
Script
7158 KB
Stylesheet
324 KB
Document
19 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
422 KB
Server response times are low (TTFB) - Root document took 190 ms
Time To First Byte identifies the time at which your server sends a response. 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.

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.

Serve images in next-gen formats
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.

Minimize Critical Requests Depth - 9 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.

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.


Page Speed (Google PageSpeed Insights) - Mobile

90
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 2.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 70 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 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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) 5067.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 4.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.5 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 2.5 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.

Avoids an excessive DOM size - 137 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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
137
Maximum DOM Depth
11
Maximum Child Elements
9
Minify JavaScript - Potential savings of 51 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB47 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB5 KB
Keep request counts low and transfer sizes small - 40 requests • 366 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
40366 KB
Image
29175 KB
Script
7158 KB
Stylesheet
324 KB
Document
19 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
422 KB
Eliminate render-blocking resources - Potential savings of 2,140 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://opolanco.es/css/reset.css
1 KB180
http://opolanco.es/css/general.css
19 KB780
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB630
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
4 KB330
http://opolanco.es/js/functions.js
3 KB330
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB1380
http://opolanco.es/js/jquery/jquery-easing.js
4 KB180
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js
1 KB180
http://opolanco.es/js/jquery/jquery-plugin-wheel.js
1 KB180
Enable text compression - Potential savings of 121 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB83 KB
http://opolanco.es/css/general.css
19 KB16 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB9 KB
http://opolanco.es/
9 KB6 KB
http://opolanco.es/js/jquery/jquery-easing.js
4 KB3 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
3 KB2 KB
http://opolanco.es/js/functions.js
3 KB2 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://opolanco.es/
0 ms501 ms9 KB9 KB200text/htmlDocument
http://opolanco.es/css/reset.css
513 ms1169 ms1 KB1 KB200text/cssStylesheet
http://opolanco.es/css/general.css
513 ms1006 ms19 KB19 KB200text/cssStylesheet
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
514 ms1005 ms13 KB13 KB200text/javascriptScript
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
514 ms847 ms4 KB3 KB200text/cssStylesheet
http://opolanco.es/js/functions.js
515 ms1002 ms3 KB3 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-1.3.2.js
515 ms1320 ms118 KB118 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-easing.js
515 ms1163 ms4 KB4 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js
515 ms1170 ms1 KB1 KB200text/javascriptScript
http://opolanco.es/js/jquery/jquery-plugin-wheel.js
516 ms1323 ms1 KB1 KB200text/javascriptScript
http://opolanco.es/css/images/blank.gif
516 ms1166 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/miga-pan.gif
516 ms1323 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/home.gif
1167 ms1347 ms1 KB1 KB200image/gifImage
http://opolanco.es/css/images/arbol-dir.gif
1324 ms1526 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/correo.gif
1342 ms1510 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/imprimir.gif
1342 ms1512 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/miga-pan-verde.gif
1342 ms1507 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/mas-azul.gif
1342 ms1662 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/miga-pan-azul-claro.gif
1342 ms1661 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/guia-paciente2.gif
1343 ms1824 ms15 KB14 KB200image/gifImage
http://opolanco.es/css/images/bolsa-trabajo2.gif
1343 ms1679 ms15 KB15 KB200image/gifImage
http://opolanco.es/css/images/cea.gif
1343 ms1675 ms10 KB10 KB200image/gifImage
http://opolanco.es/css/images/urgencias2_1.gif
1343 ms1692 ms4 KB4 KB200image/gifImage
http://opolanco.es/css/images/urgencias2_2.gif
1343 ms1823 ms7 KB6 KB200image/gifImage
http://www.w3.org/Icons/valid-xhtml10-blue
1344 ms1519 ms2 KB2 KB200image/pngImage
http://jigsaw.w3.org/css-validator/images/vcss-blue
1344 ms1519 ms2 KB2 KB200image/gifImage
http://opolanco.es/css/images/itci.gif
1344 ms1824 ms1 KB1 KB200image/gifImage
http://opolanco.es/css/images/loveo.gif
1344 ms1838 ms1 KB1 KB200image/gifImage
http://www.google-analytics.com/ga.js
1344 ms1350 ms17 KB45 KB200text/javascriptScript
http://opolanco.es/css/images/baner.gif
1347 ms2011 ms48 KB47 KB200image/gifImage
http://opolanco.es/css/images/pestana-ini.gif
1348 ms1856 ms1 KB0 KB200image/gifImage
http://opolanco.es/css/images/pestana-med.gif
1348 ms1989 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/pestana-fin.gif
1348 ms1991 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/portada.gif
1350 ms2451 ms58 KB58 KB200image/gifImage
http://opolanco.es/css/images/barra-contenidos.gif
1350 ms2001 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/separador-verde.gif
1350 ms2391 ms2 KB2 KB200image/gifImage
http://opolanco.es/css/images/login.gif
1351 ms2156 ms3 KB2 KB200image/gifImage
http://opolanco.es/css/images/siguiente-gris.gif
1353 ms2152 ms0 KB0 KB200image/gifImage
http://opolanco.es/css/images/pie.gif
1354 ms2166 ms1 KB1 KB200image/gifImage
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=2005990467&utmhn=opolanco.es&utmcs=UTF-8&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Hospital%20Obispo%20Polanco&utmhid=758245590&utmr=-&utmp=%2F&utmht=1568874736427&utmac=UA-16708699-1&utmcc=__utma%3D129689042.1300707034.1568874736.1568874736.1568874736.1%3B%2B__utmz%3D129689042.1568874736.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=2071302957&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
1423 ms1435 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 38 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://opolanco.es/js/jquery/jquery-1.3.2.js
0 ms118 KB
http://opolanco.es/css/images/portada.gif
0 ms58 KB
http://opolanco.es/css/images/baner.gif
0 ms48 KB
http://opolanco.es/css/general.css
0 ms19 KB
http://opolanco.es/css/images/bolsa-trabajo2.gif
0 ms15 KB
http://opolanco.es/css/images/guia-paciente2.gif
0 ms15 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
0 ms13 KB
http://opolanco.es/css/images/cea.gif
0 ms10 KB
http://opolanco.es/css/images/urgencias2_2.gif
0 ms7 KB
http://opolanco.es/css/images/urgencias2_1.gif
0 ms4 KB
http://opolanco.es/js/jquery/jquery-easing.js
0 ms4 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
0 ms4 KB
http://opolanco.es/js/functions.js
0 ms3 KB
http://opolanco.es/css/images/login.gif
0 ms3 KB
http://opolanco.es/css/images/separador-verde.gif
0 ms2 KB
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js
0 ms1 KB
http://opolanco.es/css/reset.css
0 ms1 KB
http://opolanco.es/css/images/pie.gif
0 ms1 KB
http://opolanco.es/css/images/home.gif
0 ms1 KB
http://opolanco.es/css/images/itci.gif
0 ms1 KB
http://opolanco.es/js/jquery/jquery-plugin-wheel.js
0 ms1 KB
http://opolanco.es/css/images/loveo.gif
0 ms1 KB
http://opolanco.es/css/images/pestana-ini.gif
0 ms1 KB
http://opolanco.es/css/images/pestana-med.gif
0 ms0 KB
http://opolanco.es/css/images/pestana-fin.gif
0 ms0 KB
http://opolanco.es/css/images/miga-pan-azul-claro.gif
0 ms0 KB
http://opolanco.es/css/images/barra-contenidos.gif
0 ms0 KB
http://opolanco.es/css/images/imprimir.gif
0 ms0 KB
http://opolanco.es/css/images/arbol-dir.gif
0 ms0 KB
http://opolanco.es/css/images/correo.gif
0 ms0 KB
http://opolanco.es/css/images/miga-pan.gif
0 ms0 KB
http://opolanco.es/css/images/miga-pan-verde.gif
0 ms0 KB
http://opolanco.es/css/images/mas-azul.gif
0 ms0 KB
http://opolanco.es/css/images/siguiente-gris.gif
0 ms0 KB
http://opolanco.es/css/images/blank.gif
0 ms0 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
http://jigsaw.w3.org/css-validator/images/vcss-blue
518400000 ms2 KB
http://www.w3.org/Icons/valid-xhtml10-blue
2592000000 ms2 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB121 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
523 ms
7 ms
532 ms
7 ms
1346 ms
14 ms
1361 ms
37 ms
1402 ms
5 ms
1412 ms
31 ms
Minify CSS - Potential savings of 6 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://opolanco.es/css/general.css
19 KB3 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
4 KB3 KB
JavaScript execution time - 0.2 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
395 ms13 ms4 ms
http://opolanco.es/js/jquery/jquery-1.3.2.js
175 ms44 ms12 ms
http://www.google-analytics.com/ga.js
121 ms116 ms5 ms
Remove unused CSS - Potential savings of 17 KB
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.

URL
SizePotential Savings
http://opolanco.es/css/general.css
19 KB13 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css
4 KB4 KB
Avoids enormous network payloads - Total size was 366 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://opolanco.es/js/jquery/jquery-1.3.2.js
118 KB
http://opolanco.es/css/images/portada.gif
58 KB
http://opolanco.es/css/images/baner.gif
48 KB
http://opolanco.es/css/general.css
19 KB
http://www.google-analytics.com/ga.js
17 KB
http://opolanco.es/css/images/bolsa-trabajo2.gif
15 KB
http://opolanco.es/css/images/guia-paciente2.gif
15 KB
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
13 KB
http://opolanco.es/css/images/cea.gif
10 KB
http://opolanco.es/
9 KB
Minimizes main-thread work - 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
235 ms
Script Evaluation
179 ms
Style & Layout
133 ms
Rendering
83 ms
Parse HTML & CSS
46 ms
Script Parsing & Compilation
29 ms
Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. 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 500 ms
Time To First Byte identifies the time at which your server sends a response. 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.

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.

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

Serve images in next-gen formats
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.

Minimize Critical Requests Depth - 9 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.

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.

General renders only 5 pixels tall (12 CSS pixels) .
Formación e Investigación and 6 others render only 5 pixels tall (12 CSS pixels) .
Inicio renders only 5 pixels tall (12 CSS pixels) .
ACTUALIDAD renders only 5 pixels tall (12 CSS pixels) .
ver todas las noticias renders only 5 pixels tall (12 CSS pixels) .
16/4/2019 and 1 others render only 5 pixels tall (12 CSS pixels) .
RESOLUCION 15-04-2019... and 1 others render only 5 pixels tall (12 CSS pixels) .
... and 1 others render only 5 pixels tall (12 CSS pixels) .
Contraseña: and 1 others render only 5 pixels tall (12 CSS pixels) .
¿Olvidó sus datos? renders only 4 pixels tall (11 CSS pixels) .
Hospital Obispo Polanco. and 1 others render only 4 pixels tall (11 CSS pixels) .
44002 TERUEL | Teléf. and 2 others render only 4 pixels tall (11 CSS pixels) .
buzgen.hopl@salud.aragon.es renders only 4 pixels tall (11 CSS pixels) .

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

Your page has 6 blocking script resources and 3 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:

http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js
http://opolanco.es/js/functions.js
http://opolanco.es/js/jquery/jquery-1.3.2.js
http://opolanco.es/js/jquery/jquery-easing.js
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js
http://opolanco.es/js/jquery/jquery-plugin-wheel.js
Optimize CSS Delivery of the following:

http://opolanco.es/css/reset.css
http://opolanco.es/css/general.css
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css

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://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css (expiration not specified)
http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js (expiration not specified)
http://opolanco.es/css/general.css (expiration not specified)
http://opolanco.es/css/images/arbol-dir.gif (expiration not specified)
http://opolanco.es/css/images/baner.gif (expiration not specified)
http://opolanco.es/css/images/barra-contenidos.gif (expiration not specified)
http://opolanco.es/css/images/blank.gif (expiration not specified)
http://opolanco.es/css/images/bolsa-trabajo2.gif (expiration not specified)
http://opolanco.es/css/images/cea.gif (expiration not specified)
http://opolanco.es/css/images/correo.gif (expiration not specified)
http://opolanco.es/css/images/guia-paciente2.gif (expiration not specified)
http://opolanco.es/css/images/home.gif (expiration not specified)
http://opolanco.es/css/images/imprimir.gif (expiration not specified)
http://opolanco.es/css/images/itci.gif (expiration not specified)
http://opolanco.es/css/images/login.gif (expiration not specified)
http://opolanco.es/css/images/loveo.gif (expiration not specified)
http://opolanco.es/css/images/mas-azul.gif (expiration not specified)
http://opolanco.es/css/images/miga-pan-azul-claro.gif (expiration not specified)
http://opolanco.es/css/images/miga-pan-verde.gif (expiration not specified)
http://opolanco.es/css/images/miga-pan.gif (expiration not specified)
http://opolanco.es/css/images/pestana-fin.gif (expiration not specified)
http://opolanco.es/css/images/pestana-ini.gif (expiration not specified)
http://opolanco.es/css/images/pestana-med.gif (expiration not specified)
http://opolanco.es/css/images/pie.gif (expiration not specified)
http://opolanco.es/css/images/portada.gif (expiration not specified)
http://opolanco.es/css/images/separador-verde.gif (expiration not specified)
http://opolanco.es/css/images/siguiente-gris.gif (expiration not specified)
http://opolanco.es/css/images/urgencias2_1.gif (expiration not specified)
http://opolanco.es/css/images/urgencias2_2.gif (expiration not specified)
http://opolanco.es/css/reset.css (expiration not specified)
http://opolanco.es/js/functions.js (expiration not specified)
http://opolanco.es/js/jquery/jquery-1.3.2.js (expiration not specified)
http://opolanco.es/js/jquery/jquery-easing.js (expiration not specified)
http://opolanco.es/js/jquery/jquery-plugin-bgpos.js (expiration not specified)
http://opolanco.es/js/jquery/jquery-plugin-wheel.js (expiration not specified)
http://www.google-***ytics.com/ga.js (2 hours)

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 id="menu11" href="./general.php" class="a1">General</a> is close to 2 other tap targets .
The tap target <a id="menu12" href="./ciudadano.php" class="a2">Ciudadano</a> and 6 others are close to other tap targets .
The tap target <a href="#tab2" class="a3"></a> is close to 5 other tap targets .
The tap target <a href="./index.php">Inicio</a> is close to 2 other tap targets .
The tap target <a href="./index.php"></a> and 3 others are close to other tap targets .
The tap target <a href="agenda-noticias.php">ver todas las noticias</a> is close to 3 other tap targets .
The tap target <label>Usuario:</label> and 1 others are close to other tap targets .
The tap target <label>Usuario:</label> and 3 others are close to other tap targets .
The tap target <input id="enviar" type="submit" name="enviar"> is close to 4 other tap targets .
The tap target <a href="recordar.php">¿Olvidó sus datos?</a> is close to 3 other tap targets .
The tap target <a href="http://www.boloncol.com/"></a> and 1 others are close to other tap targets .
The tap target <a href="http://jigsaw.…css-validator/"></a> is close to 1 other tap targets .
The tap target <a href="http://www.itcy.es/"></a> and 1 others are close to other tap targets .

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 122.5KiB (71% reduction).

Compressing http://opolanco.es/js/jquery/jquery-1.3.2.js could save 83.4KiB (70% reduction).
Compressing http://opolanco.es/css/general.css could save 15.6KiB (82% reduction).
Compressing http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js could save 9KiB (70% reduction).
Compressing http://opolanco.es/ could save 6KiB (68% reduction).
Compressing http://opolanco.es/js/jquery/jquery-easing.js could save 2.8KiB (77% reduction).
Compressing http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css could save 2.3KiB (66% reduction).
Compressing http://opolanco.es/js/functions.js could save 2KiB (64% reduction).
Compressing http://opolanco.es/js/jquery/jquery-plugin-bgpos.js could save 689B (57% reduction).
Compressing http://opolanco.es/css/reset.css could save 423B (46% reduction).
Compressing http://opolanco.es/js/jquery/jquery-plugin-wheel.js could save 266B (42% reduction).

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.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 52.6KiB (39% reduction).

Minifying http://opolanco.es/js/jquery/jquery-1.3.2.js could save 46.4KiB (40% reduction).
Minifying http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.js could save 4.4KiB (35% reduction).
Minifying http://opolanco.es/js/functions.js could save 1.4KiB (46% reduction).
Minifying http://opolanco.es/js/jquery/jquery-plugin-bgpos.js could save 399B (34% reduction).

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 5.5KiB (24% reduction).

Minifying http://opolanco.es/css/SpryAssets/SpryCollapsiblePanel.css could save 2.8KiB (80% reduction).
Minifying http://opolanco.es/css/general.css could save 2.6KiB (14% reduction).
Minifying http://opolanco.es/css/reset.css could save 180B (20% reduction).

Optimize images

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

Optimize the following images to reduce their size by 4.2KiB (36% reduction).

Compressing http://opolanco.es/css/images/login.gif could save 1.2KiB (51% reduction).
Compressing http://opolanco.es/css/images/pie.gif could save 773B (89% reduction).
Compressing http://opolanco.es/css/images/home.gif could save 738B (86% reduction).
Compressing http://opolanco.es/css/images/separador-verde.gif could save 576B (34% reduction).
Compressing http://opolanco.es/css/images/urgencias2_1.gif could save 488B (13% reduction).
Compressing http://jigsaw.w3.org/css-validator/images/vcss-blue could save 291B (17% reduction).
Compressing http://opolanco.es/css/images/loveo.gif could save 139B (23% reduction).

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 1,017B (12% reduction).

Minifying http://opolanco.es/ could save 1,017B (12% reduction).
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.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does opolanco.es use compression?

opolanco.es does not use compression.
Original size: 8.71 KB
Compressed size: n/a
File reduced by: n/a

+ 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

opolanco.es does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

opolanco.es does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Salud/Clínicas y hospitales

+ Http Header

Date: Thu, 19 Sep 2019 06:32:03 GMT
Server: Apache
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
TXT 3600
MX mx.buzondecorreo.com 3600
A 217.76.150.74 60
SOA 3600
Mname ns1.piensasolutions.com
Rname hostmaster.piensasolutions.com
Serial Number 2006101854
Refresh 21600
Retry 3600
Expire 2419200
Minimum TTL 0
NS ns2.piensasolutions.com 3600
NS ns1.piensasolutions.com 3600

+ Whois Lookup

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

whois lookup at whois.nic.es...
Conditions of use for the whois service via port 43 for .es domains

Access will only be enabled for IP addresses authorised by Red.es. A maximum of one IP address per
user/organisation is permitted.

Red.es accepts no responsibility whatsoever for the availability of access to WHOIS, which may be
suspended at any time and without prior warning at the discretion of the public entity.

The service will be limited to the data established by Red.es.

The user promises to make use of the service and to carry out any action derived from the aforesaid
use in accordance with current applicable regulations, in particular with legislation on “.es” domain
names and personal data protection.

In particular, the user undertakes not to use the service to carry out abusive or speculative domain
name registrations, pursuant to section 5 of the Sixth Additional Provision of Law 34/2002, of 11 July,
on Services of the Information Society and Electronic Commerce. Likewise, the User undertakes not to
use the service to obtain data, the possession of which may contravene the provisions of Organic Law
15/1999, of 13 December, on Personal Data Protection, and its Regulations, or in Law 34/2002, of 11
July, on Services of the Information Society and Electronic Commerce.

Failure to comply with these conditions will result in the immediate withdrawal of the service and any
registered domain name which breaches said conditions may be officially cancelled by Red.es.
-------------------------------------------------------------------------------------------------------


The IP address used to perform the query is not authorised or has exceeded the established limit for
queries.To request access to the service,complete the form located at https://sede.red.gob.es/sede/whois,
where you may also consult the service conditions.

-------------------------------------------------------------------------------------------------------
More information on each domain may be consulted at www.dominios.es.
Last update was 34 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with opolanco.es 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!
opolanco.es widget