medipedia.pt

medipedia.pt is SSL secured

Free website and domain report on medipedia.pt

Last Updated: 11th April, 2021 Update Now
Overview

Snoop Summary for medipedia.pt

This is a free and comprehensive report about medipedia.pt. The domain medipedia.pt is currently hosted on a server located in Netherlands with the IP address 5.79.97.201, where EUR is the local currency and the local language is Dutch. Medipedia.pt has the potential to be earning an estimated $4 USD per day from advertising revenue. If medipedia.pt was to be sold it would possibly be worth $2,584 USD (based on the daily revenue potential of the website over a 24 month period). Medipedia.pt is quite popular with an estimated 1,237 daily unique visitors. This report was last updated 11th April, 2021.

About medipedia.pt

Site Preview: medipedia.pt medipedia.pt
Title:
Description: Medipédia, Conteúdos de Saúde
Keywords and Tags: blogs, health, wiki
Related Terms: agregador de conteudos
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$2,584 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 685,367
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,237
Monthly Visitors: 37,650
Yearly Visitors: 451,505
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $107 USD
Yearly Revenue: $1,287 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: medipedia.pt 12
Domain Name: medipedia 9
Extension (TLD): pt 2

Page Speed Analysis

Average Load Time: 0.78 seconds
Load Time Comparison: Faster than 78% of sites

PageSpeed Insights

Avg. (All Categories) 60
Performance 53
Accessibility 58
Best Practices 73
SEO 82
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.medipedia.pt/
Updated: 11th April, 2021

1.10 seconds
First Contentful Paint (FCP)
72%
24%
4%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
53

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for medipedia.pt. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 10 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 2.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive medipedia.pt as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://medipedia.pt/
http/1.1
0
387.95699999901
383
0
302
text/html
https://medipedia.pt/
http/1.1
389.07999999356
1195.8839999861
413
0
301
text/html
https://www.medipedia.pt/
http/1.1
1196.4640000369
2441.2289999891
13052
56481
200
text/html
Document
https://www.medipedia.pt/templates/default/css/style_v2.css
http/1.1
2457.5879999902
3503.9749999996
24709
156596
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/js/fancybox/jquery.fancybox-1.3.1.css
http/1.1
2457.7089999802
7353.2610000111
1597
6348
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/js/qtip/jquery.qtip.css
http/1.1
2457.8779999865
8057.461999997
2617
9416
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/js/jquery-1.6.1.min.js
http/1.1
2458.1640000106
7456.204999995
32360
91898
200
text/javascript
Script
https://www.medipedia.pt/templates/default/js/geral.js
http/1.1
2458.3829999901
7374.7449999792
3604
13396
200
application/javascript
Script
https://www.medipedia.pt/templates/default/js/pesquisa_solr.js
http/1.1
2458.7480000337
6045.4749999917
5329
19445
200
application/javascript
Script
https://www.medipedia.pt/templates/default/js/fancybox/jquery.fancybox-1.3.1.js
http/1.1
2459.1399999917
5339.7230000119
5505
14800
200
text/javascript
Script
https://www.medipedia.pt/templates/default/js/qtip/jquery.qtip.js
http/1.1
2459.4170000055
6453.5460000043
15848
42931
200
text/javascript
Script
https://www.medipedia.pt/templates/default/js/jquery.session.js
http/1.1
2459.7490000306
3375.7310000365
1131
2028
200
text/javascript
Script
https://www.medipedia.pt/templates/default/js/Nibbler.min.js
http/1.1
2459.9649999873
3366.4890000364
983
920
200
text/javascript
Script
https://www.medipedia.pt/templates/default/js/facebook.js?1618130353
http/1.1
2460.0970000029
3389.8279999848
1478
2550
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans:400,600,800,700
h2
2460.2540000342
2477.7950000134
1462
8424
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Droid+Sans:400,700
h2
2460.6110000168
2480.018000002
1067
764
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/js/jquery.jsonSuggest_pesquisa.js
http/1.1
2460.7599999872
7787.7720000106
2199
4076
200
text/javascript
Script
https://www.medipedia.pt/templates/default/js/farmacia.js
http/1.1
2461.1049999949
7365.6630000332
1455
2859
200
application/javascript
Script
https://www.medipedia.pt/templates/default/js/pesquisar.js
http/1.1
2461.2930000294
5348.8639999996
7164
36602
200
application/javascript
Script
https://www.medipedia.pt/templates/default/js/inicio.js
http/1.1
2461.5859999903
7361.2510000239
833
797
200
text/javascript
Script
https://www.medipedia.pt/templates/default/leafletmaps/js/MapManager.js
http/1.1
2461.7340000113
6336.0550000216
3769
15588
200
application/javascript
Script
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet.js
http/1.1
2461.9400000083
6549.3160000187
41114
141125
200
application/javascript
Script
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet-providers.js
http/1.1
2462.0540000033
3391.0560000222
6902
22850
200
application/javascript
Script
https://www.medipedia.pt/templates/default/leafletmaps/js/all.js
http/1.1
2462.3439999996
3612.8589999862
415106
1174322
200
application/javascript
Script
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet.awesome-markers.js
http/1.1
2462.5160000287
6344.4110000273
2006
6240
200
application/javascript
Script
https://www.medipedia.pt/templates/default/leafletmaps/handling/leaflet-gesture-handling.js
http/1.1
2462.9190000123
8063.1380000268
8232
35680
200
application/javascript
Script
https://www.medipedia.pt/templates/default/js/google.js
http/1.1
2463.1120000267
7352.1600000095
2585
10778
200
application/javascript
Script
https://www.medipedia.pt/templates/default/css/jQueryThemes/start/jquery-ui-json-suggest_v2.css
http/1.1
2463.4739999892
4327.5830000057
3028
14463
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/leafletmaps/css/mapstyle.css
http/1.1
2463.6119999923
7364.3070000107
708
562
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/leafletmaps/css/leaflet.css
http/1.1
2463.7210000074
7365.0800000178
3705
14130
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/leafletmaps/css/all.css
http/1.1
2463.8489999925
5454.756000021
12807
68243
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/leafletmaps/css/leaflet.awesome-markers.css
http/1.1
2464.1640000045
3361.5059999865
1053
2329
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/leafletmaps/handling/leaflet-gesture-handling.css
http/1.1
2464.2960000201
3390.2569999918
874
1258
200
text/css
Stylesheet
https://www.medipedia.pt/templates/default/images/v2/logotipo.png
http/1.1
8155.3249999997
10384.477999993
3106
2730
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/bt_pesquisa.png
http/1.1
8155.476999993
10054.255000025
637
262
200
image/png
Image
https://pagead2.googlesyndication.com/pagead/show_ads.js
h2
8058.5280000232
8071.2930000154
33487
93951
200
text/javascript
Script
https://www.medipedia.pt/templates/default/images/v2/facebook_banner.png
http/1.1
8155.6759999949
9100.8830000064
22451
22073
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/front_medicos.png
http/1.1
8155.8180000284
9762.7000000211
169196
168816
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/barra_separadora.png
http/1.1
8155.9100000304
8967.2160000191
512
138
200
image/png
Image
https://www.medipedia.pt/home/components/images/spotimages/2.jpg
http/1.1
8156.1360000051
8761.1669999897
26550
26172
200
image/jpeg
Image
https://www.medipedia.pt/templates/default/images/v2/anf.png
http/1.1
8156.2300000223
8652.8169999947
978
604
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/i2_facebook.png
http/1.1
8156.3239999814
10379.873000027
701
326
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/i2_tweeter.png
http/1.1
8156.427000009
8666.3190000108
714
340
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/i2_google.png
http/1.1
8156.5100000007
8966.9100000174
736
361
200
image/png
Image
https://static.getclicky.com/js
h2
8146.4430000051
8218.7990000239
6156
15717
200
text/javascript
Script
https://connect.facebook.net/pt_PT/sdk.js
h2
8156.5929999924
8188.4220000356
2685
3224
200
application/x-javascript
Script
https://www.medipedia.pt/templates/default/images/v2/background.png
http/1.1
8160.3539999924
8695.83099999
821
447
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
h2
8162.1410000371
8165.7620000187
9694
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
h2
8162.2639999841
8166.1409999942
9643
9080
200
font/woff2
Font
https://pagead2.googlesyndication.com/pagead/js/r20210406/r20190131/show_ads_impl_fy2019.js
h2
8183.2789999899
8205.8379999944
84673
224589
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/html/r20210406/r20190131/zrt_lookup.html
h2
8191.4189999807
8195.8539999905
5404
10289
200
text/html
Document
https://www.medipedia.pt/templates/default/images/v2/interrogacao_redondo.png
http/1.1
8199.9059999944
8686.0689999885
642
268
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/marqueconsulta-submit.png
http/1.1
8203.4560000175
8694.7689999943
2120
1745
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/barra_separadora_in.png
http/1.1
8204.0249999845
11038.922999986
480
106
200
image/png
Image
https://www.medipedia.pt//painel/open_image/fotos/eXW6VJxhHnkS.jpg/55
http/1.1
8204.3070000364
11886.164000025
4832
4438
200
image/jpeg
Image
https://www.medipedia.pt//painel/open_image/fotos/sjzjoggozfpw6svv.png/55
http/1.1
8204.4829999795
11769.969000015
8652
8234
200
image/png
Image
https://www.medipedia.pt//painel/open_image/fotos/5hr75mjckf46ga5y.png/55
http/1.1
8204.8170000198
11378.965999989
8182
7789
200
image/png
Image
https://www.medipedia.pt//painel/open_image/fotos/PnyG7zhRI29z.jpg/55
http/1.1
8205.1140000112
12014.147999987
4001
3607
200
image/jpeg
Image
https://www.medipedia.pt//painel/open_image/fotos/h8PgmStrc6fn.png/55
http/1.1
8205.346999981
11618.492999987
5244
4851
200
image/png
Image
https://www.medipedia.pt//painel/open_image/fotos/xyPabpU7kvMv.jpg/55
http/1.1
8206.612000009
11242.443000025
3939
3545
200
image/jpeg
Image
https://www.medipedia.pt//painel/open_image/fotos/J5ApWt4E4ldg.jpg/55
http/1.1
8206.8399999989
11484.101000009
4906
4511
200
image/jpeg
Image
https://www.medipedia.pt/templates/default/images/v2/seta_todos.png
http/1.1
8207.0010000025
8686.4659999846
3259
2884
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/barra_separadora_cat.png
http/1.1
8207.144999993
8964.8160000215
488
114
200
image/png
Image
https://ssl.google-analytics.com/ga.js
h2
8227.3879999993
8233.9369999827
17798
46274
200
text/javascript
Script
https://www.medipedia.pt/templates/default/images/v2/box_1.png
http/1.1
8229.542999994
8693.8680000021
1835
1460
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/box_2.png
http/1.1
8229.8210000154
8969.3800000241
1730
1354
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/box_3.png
http/1.1
8230.2290000371
8656.1179999844
1757
1382
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/novidade-submit.png
http/1.1
8230.5620000116
8687.1740000206
3316
2941
200
image/png
Image
https://www.medipedia.pt/templates/default/images/v2/farmacias-submit.png
http/1.1
8230.9550000355
9047.0390000264
624
250
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
h2
8231.7100000218
8234.9110000068
9743
9180
200
font/woff2
Font
https://connect.facebook.net/pt_PT/sdk.js?hash=8e3d097f621da3094a9cc1f914482489&ua=modern_es6
h2
8247.2459999844
8282.28699998
66537
221331
200
application/x-javascript
Script
https://partner.googleadservices.com/gampad/cookie.js?domain=www.medipedia.pt&callback=_gfp_s_&client=ca-pub-8046867249897342
h2
8323.1399999931
8327.4119999842
840
202
200
text/javascript
Script
https://adservice.google.com/adsid/integrator.js?domain=www.medipedia.pt
h2
8324.9199999846
8329.6410000185
763
107
200
application/javascript
Script
https://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-8046867249897342&output=html&h=90&slotname=8031613925&adk=3956361427&adf=813951275&pi=t.ma~as.8031613925&w=728&lmt=1618130359&url=https%3A%2F%2Fwww.medipedia.pt%2F&flash=0&wgl=1&dt=1618130359495&bpp=20&bdt=5725&idt=134&shv=r20210406&cbv=r20190131&ptt=5&saldr=sa&abxe=1&correlator=1767588049093&frm=20&pv=2&ga_vid=1085412387.1618130360&ga_sid=1618130360&ga_hid=1378306091&ga_fc=0&u_tz=-420&u_his=2&u_java=0&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_nplug=0&u_nmime=0&adx=176&ady=169&biw=1350&bih=940&scr_x=0&scr_y=0&eid=44740079%2C44739387&oid=3&pvsid=1616256539841695&pem=373&eae=0&fc=640&brdim=0%2C0%2C0%2C0%2C800%2C0%2C1%2C1%2C1350%2C940&vis=1&rsz=%7C%7ClE%7C&abl=CS&pfx=0&fu=0&bc=31&ifi=1&uci=a!1&fsb=1&xpc=Helk7lLNex&p=https%3A//www.medipedia.pt&dtd=165
h2
8339.0720000025
8586.3470000331
23543
60663
200
text/html
Document
https://www.googletagservices.com/activeview/js/current/osd.js?cb=%2Fr20100101
h2
8342.4280000036
8350.2750000334
28786
75208
200
text/javascript
Script
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=873186700&utmhn=www.medipedia.pt&utmcs=windows-1252&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Medip%C3%A9dia%2C%20Conte%C3%BAdos%20de%20Sa%C3%BAde&utmhid=1378306091&utmr=-&utmp=%2F&utmht=1618130359686&utmac=UA-5525841-2&utmcc=__utma%3D29087904.1085412387.1618130360.1618130360.1618130360.1%3B%2B__utmz%3D29087904.1618130360.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=1772706302&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAQAAAAE~
http/1.1
8372.2549999948
8385.0279999897
757
0
302
text/html
https://ssl.google-analytics.com/__utm.gif?utmwv=5.7.2&utms=2&utmn=1995455863&utmhn=www.medipedia.pt&utmcs=windows-1252&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Medip%C3%A9dia%2C%20Conte%C3%BAdos%20de%20Sa%C3%BAde&utmhid=1378306091&utmr=-&utmp=%2F&utmht=1618130359693&utmac=UA-26197616-1&utmcc=__utma%3D29087904.1085412387.1618130360.1618130360.1618130360.1%3B%2B__utmz%3D29087904.1618130360.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=&utmmt=1&utmu=qhAAAAAAAAAAAAAAAAQAAAAE~
h2
8372.520999983
8375.8699999889
602
35
200
image/gif
Image
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-5525841-2&cid=1085412387.1618130360&jid=1772706302&_v=5.7.2&z=873186700
http/1.1
8385.306000011
8402.5869999896
826
0
302
text/html
https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-5525841-2&cid=1085412387.1618130360&jid=1772706302&_v=5.7.2&z=873186700
h2
8402.7810000116
8409.3890000368
678
42
200
image/gif
Image
https://in.getclicky.com/in.php?site_id=81103&type=pageview&href=%2F&title=Medip%C3%A9dia%2C%20Conte%C3%BAdos%20de%20Sa%C3%BAde&res=800x600&lang=en&jsuid=2913791820&mime=js&x=0.4630267544438369
h2
8457.1599999908
8780.5360000348
586
173
200
text/javascript
Script
https://tpc.googlesyndication.com/simgad/3591994845642353856?sqp=4sqPyQQ7QjkqNxABHQAAtEIgASgBMAk4A0DwkwlYAWBfcAKAAQGIAQGdAQAAgD-oAQGwAYCt4gS4AV_FAS2ynT4&rs=AOga4qnTBXb2uidyVhaajNfMb1GQZt_Cug
h2
8601.238000032
8608.3259999868
45783
45189
200
image/png
Image
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/abg_lite_fy2019.js
h2
8601.6030000173
8604.999000032
7895
17643
200
text/javascript
Script
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/client/window_focus_fy2019.js
h2
8608.8800000143
8611.9630000321
2084
2513
200
text/javascript
Script
https://www.googletagservices.com/activeview/js/current/rx_lidar.js?cache=r20110914
h2
8607.919000031
8616.3919999963
37234
120827
200
text/javascript
Script
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/client/qs_click_protection_fy2019.js
h2
8608.1330000306
8614.1840000055
6379
12947
200
text/javascript
Script
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/client/one_click_handler_one_afma_fy2019.js
h2
8609.0390000027
8614.682000014
11260
25561
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/adview?ai=CqNQxt7VyYOeVKY2thwfe6Y2ABOuGrJtimpDtn9cNv-EeEAEgrd2CE2DJlvKKtKTYD6AB_pamuwLIAQKoAwHIA8kEqgS_AU_Qado_7yBCrTlhl-tIs_RlrljUiQ2yrGRxlkraMZXhtJau0n9JhtE7lYNeZ0BF30N3Ak3JP_PHSFvQadkngAuJ6654s84Ix7WQftdRtwci2IPuSCCeaxsAgEFKeIrSEHI7N-1ZBknfoZWLYJ2zfc4hjTtpjMKlx0lYHS65V4kQDQxyqKAyTwAypGimHe4FghiXe318UzBI5dxUYLPOIKQ1foPJrjP1qXUU3E73MtMgUy3ZOObhACGP6hdaavcrwATOj9GR8AKgBgKAB-ro2cQBqAfVyRuoB_DZG6gH8tkbqAeOzhuoB5PYG6gHugaoB-6WsQKoB6a-G6gH7NUb2AcB8gcEEIqOD9IIBwiAYRABGB-ACgHICwHYEwOyFxoKGAgAEhRwdWItODA0Njg2NzI0OTg5NzM0Mg&sigh=HuAKezouNbQ&tpd=AGWhJmt4LPgLTTIAac8vf_stXX9wa_ahagaRToFp4ygGRuiINQ
h2
8609.6700000344
8629.0540000191
1038
0
200
text/html
Fetch
https://googleads.g.doubleclick.net/pagead/drt/s?v=r20120211
h2
8629.7210000339
8633.1239999854
574
143
200
text/html
Document
data
8692.9029999883
8692.9510000045
0
216
200
image/png
Image
https://www.google.com/pagead/drt/ui
http/1.1
8779.784000013
8787.2910000151
515
0
302
text/html
https://pagead2.googlesyndication.com/bg/rg7ZOtwj_KsF30rM_Y0_DmvJrp5jy6rfjTYWIxfvKAc.js
h2
8782.6230000355
8788.4590000031
6284
14465
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/drt/si
h2
8787.834000017
8792.1610000194
717
0
200
text/html
Document
https://googleads.g.doubleclick.net/pagead/adview?ai=CFvJtt7VyYOeVKY2thwfe6Y2ABOuGrJtimpDtn9cNv-EeEAEgrd2CE2DJlvKKtKTYD6AB_pamuwLIAQKoAwGqBL8BT9Bp2j_vIEKtOWGX60iz9GWuWNSJDbKsZHGWStoxleG0lq7Sf0mG0TuVg15nQEXfQ3cCTck_88dIW9Bp2SeAC4nrrnizzgjHtZB-11G3ByLYg-5IIJ5rGwCAQUp4itIQcjs37VkGSd-hlYtgnbN9ziGNO2mMwqXHSVgdLrlXiRANDHKooDJPADKkaKYd7gWCGJd7fXxTMEjl3FRgs84gpDV-g8muM_WpdRTcTvcy0yBTLdk45uEAIY_qF1pq9yvABM6P0ZHwAqAGAoAH6ujZxAGoB9XJG6gH8NkbqAfy2RuoB47OG6gHk9gbqAe6BqgH7paxAqgHpr4bqAfs1RvYBwHyBwQQio4P0ggHCIBhEAEYH4AKAcgLAdgTA7IXGgoYCAASFHB1Yi04MDQ2ODY3MjQ5ODk3MzQy&sigh=rGarMf4nSa8&vt=1
h2
9704.5640000142
9713.974000013
653
0
200
text/html
Fetch
https://pagead2.googlesyndication.com/pcs/activeview?xai=AKAOjssoXtmNRTVBeoyGgASIiJBMfyS-c9-xIvYl3WedcBjDKEZTCNvhPVLCIx0gBOW-_SyyQDgg5kD9THpFvVxdaXC3nL15Ek0hih4wRqaL1c8VkkIoWXG8NpgmN6w&sai=AMfl-YTOTP7lp2j2RbNUbfzOMc2a580i2sG_5xaMuM_cCa2kACywtTOcaSeVxxljr8_W7khnacn8Iv0RrWx6&sig=Cg0ArKJSzOM8d5VRgh1REAE&id=osdim&mcvt=1000&p=169,176,259,904&mtos=1000,1000,1000,1000,1000&tos=1000,0,0,0,0&v=20210409&bin=7&avms=nio&bs=0,0&mc=1&if=1&app=0&itpl=4&adk=3956361427&rs=2&met=mue&la=0&cr=0&osd=1&vs=4&rst=1618130359666&dlt=250&rpt=94&isd=0&msd=0&r=v&uup=0
h2
9705.3230000311
9711.3959999988
700
42
200
image/gif
Fetch
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
h2
12016.262000019
12032.127999992
49183
138320
200
text/javascript
Script
https://pagead2.googlesyndication.com/getconfig/sodar?sv=200&tid=gda&tv=r20210406&st=env
h2
12017.993999994
12026.951000036
7134
8479
200
application/json
XHR
https://tpc.googlesyndication.com/sodar/sodar2.js
h2
12030.014000018
12034.968000022
6960
17641
200
text/javascript
Script
https://tpc.googlesyndication.com/sodar/sodar2/222/runner.html
h2
12043.89000003
12048.852999986
5619
12779
200
text/html
Document
https://adservice.google.com/adsid/integrator.js?domain=www.medipedia.pt
h2
12071.644000011
12077.315000002
763
107
200
application/javascript
Script
https://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-8046867249897342&output=html&adk=1812271804&adf=3025194257&lmt=1618130363&plat=1%3A32776%2C2%3A32776%2C9%3A32776%2C16%3A8388608%2C17%3A32%2C24%3A32%2C25%3A32%2C30%3A1081344%2C32%3A32&format=0x0&url=https%3A%2F%2Fwww.medipedia.pt%2F&ea=0&flash=0&pra=7&wgl=1&dt=1618130363383&bpp=5&bdt=9613&idt=5&shv=r20210406&cbv=r20190131&ptt=9&saldr=aa&abxe=1&cookie=ID%3D8b3b4cb3bbfad3fd-2235da21647a0089%3AT%3D1618130359%3ART%3D1618130359%3AS%3DALNI_MY9TfYXeqC0bpiqETQm2MLlQyCd3w&prev_slotnames=8031613925&nras=1&correlator=1767588049093&frm=20&pv=1&ga_vid=1085412387.1618130360&ga_sid=1618130360&ga_hid=1378306091&ga_fc=1&u_tz=-420&u_his=2&u_java=0&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_nplug=0&u_nmime=0&adx=-12245933&ady=-12245933&biw=1350&bih=940&scr_x=0&scr_y=0&eid=44740079%2C44739387&oid=3&psts=AGkb-H_rxT9L9zq42CsHbAGJaX_T4pV05-9oe1aXCK6dsMbhRjduhGWdzTAi2Pm9EXpLC1pQbtHqNEBX-Gs&pvsid=1616256539841695&pem=373&eae=2&fc=1920&brdim=0%2C0%2C0%2C0%2C800%2C0%2C1%2C1%2C1350%2C940&vis=1&rsz=%7C%7Cs%7C&abl=NS&fu=0&bc=31&ifi=2&uci=a!2&fsb=1&dtd=16
h2
12078.13400001
12156.666000024
647
54
200
text/html
Document
https://pagead2.googlesyndication.com/bg/rg7ZOtwj_KsF30rM_Y0_DmvJrp5jy6rfjTYWIxfvKAc.js
h2
12111.870000022
12115.572999988
6284
14465
200
text/javascript
Script
https://pagead2.googlesyndication.com/pagead/gen_204?id=sodar2&v=222&t=2&li=gda_r20210406&jk=1616256539841695&bg=!WlmlWR3NAAY56aLOOek7ACkAdvg8WhCGkQlLz-_vsTCwGZ51p1G3ynaqZ0DrBXWQjz3xyCMfjfCR2gIAAAC-UgAAABNoAQcKAZhUjeYoO1ROvbYfiMh-WO9bFocrsiahaH-Q8zUPhMXK0QffEYo5gHC_CZZAhKnupubg6ckAE48SkfRGLXVGvPZfW4ifwLp-IkBffgCGx-oODBjs522a3C8w-4sOp2K4RatYOi63loTww8CKAVDLwaA5Redu0DktSWZgtubMUopEKXLQk4DNnVdHwZznBCRnoxTf3vZXQtNOeyQD-xv53CEz-X5gOuAsTUSL9AicO3O9Qs6uSKGeYdNMIwqTpbOqbmvxH6sGyAyHYVi900QMQ-wUp3TbOr43ggw-9LNQsSFqY-oGXC9RLudG-fTE9vJy4wsDofeXgfY_L3uludyqPUkpEr1GT7pCTilCdAvsD5AkPCwB0-9ifaWgYXOhcbOEod66gO0o7FQ0gaermdu06cPSX58t6H8DNpiYKQqx3v1XL9NCgs2U4K7Btdr1n1aF9IpHkquXuoWq1i9g5JdA9zOVfs1jjEfdG0cjK5URQzShOzyEXC1s7_3ZIWGhXV_Gu0oyzC16qulZMlDBhLbc-b9dwiX7bbNT12KZAeIpKcsdaC4Mof5uPFPAeozLUg6EH_gz8Kb9cdNlEFWPm2BOpfcRzMywYVYP1x1-IXOwDONFJ3o5WtKLpEG4hGpyTXQYgI7g9ETgzDUk8qQ70AtaTnUVceGiUHUg7IHfVEniEjs-svD7gRxwBs0uilyXxDO0eZbW9Z2DE59-Z7_tNlRagHs1sbH1jOLHPogk8257jVn_lnVi05nL4PtFZ67NkotApPJlejqPOTAfVPnqPK-iB_2Mzi6xhk-bHbwT3QRWJx4jQ7QU5FxvInIUmMWQicZNqfyTWSBACcxaSOk2dTUqYslysIikaPRNf4yUj9cWVTnZOFgvDF-lE2hH9_qzxANnu-xWBBmElogciq0WspgpWHVGN-B_LeZBHJ5Sn2NNxuzv4SCkkF_zY3VWl9NZNqKtnC_XYFrYiXO47yGqci6yUJKbWQ1cA8Fgb8kyWEmgl7hgNa5FIDwaLOF8W5-F1PfW-EHKwpFWii9UAV1E1pOzsBXaRqvNMYE2uXkbVSplmxgZaIW15RBtCvEU_qMulExxBB_38go9qkOk0nIKcf36N0A7on0kGop0im5Pc-4k1rxWmSk0T1MAdAkZ2oFTxhOw8CJMBMP0p_kWsGA7rC0eAZrYzyqVgbrq2eoKn2oLtA
h2
12343.142000027
12348.53800002
606
0
204
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
2488.743
8.332
2501.313
9.246
3550.216
6.137
8103.799
85.349
8191.061
10.57
8201.644
8.818
8211.23
28.812
8243.477
18.717
8263.983
5.866
8272.602
12.03
8294.093
36.046
8335.693
52.324
8391.234
26.064
8417.308
6.235
8430.223
16.004
8451.869
29.437
8496.228
6.453
8634.368
6.967
8645.279
11.409
8664.255
6.215
8678.257
60.092
8738.383
6.279
8754.27
6.651
8769.392
9.906
8809.045
13.9
8834.238
108.948
8943.705
7.087
9255.023
7.565
9262.604
5.13
9969.703
7.867
12059.38
11.678
12080.612
7.722
12089.038
36.728
12125.958
7.611
12161.412
18.182
12181.172
11.774
12193.012
11.678
12204.741
6.485
12211.665
11.612
12232.32
12.419
12249.929
12.095
12262.042
5.583
12272.665
11.523
12285.128
6.881
12292.921
12.27
12306.191
12.789
12319.931
12.611
12333.488
19.444
12374.597
7.947
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 21 KiB
Images can slow down the page's load time. Medipedia.pt should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.medipedia.pt/home/components/images/spotimages/2.jpg
26172
21370
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Medipedia.pt should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 6 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Medipedia.pt should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.medipedia.pt/templates/default/css/style_v2.css
24709
3975
https://www.medipedia.pt/templates/default/leafletmaps/css/all.css
12807
2221
Minify JavaScript — Potential savings of 2 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Medipedia.pt should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.medipedia.pt/templates/default/leafletmaps/js/MapManager.js
3769
2215
Remove unused CSS — Potential savings of 34 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Medipedia.pt should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.medipedia.pt/templates/default/css/style_v2.css
24709
22435
https://www.medipedia.pt/templates/default/leafletmaps/css/all.css
12807
12807
Remove unused JavaScript — Potential savings of 153 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://pagead2.googlesyndication.com/pagead/js/r20210406/r20190131/show_ads_impl_fy2019.js
84673
46354
https://connect.facebook.net/pt_PT/sdk.js?hash=8e3d097f621da3094a9cc1f914482489&ua=modern_es6
66537
45159
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet.js
41114
34417
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
49183
30280
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Medipedia.pt should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet.js
6280
https://www.medipedia.pt/templates/default/leafletmaps/js/all.js
59
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.medipedia.pt/templates/default/images/v2/front_medicos.png
0

Diagnostics

Avoids enormous network payloads — Total size was 1,376 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.medipedia.pt/templates/default/leafletmaps/js/all.js
415106
https://www.medipedia.pt/templates/default/images/v2/front_medicos.png
169196
https://pagead2.googlesyndication.com/pagead/js/r20210406/r20190131/show_ads_impl_fy2019.js
84673
https://connect.facebook.net/pt_PT/sdk.js?hash=8e3d097f621da3094a9cc1f914482489&ua=modern_es6
66537
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js
49183
https://tpc.googlesyndication.com/simgad/3591994845642353856?sqp=4sqPyQQ7QjkqNxABHQAAtEIgASgBMAk4A0DwkwlYAWBfcAKAAQGIAQGdAQAAgD-oAQGwAYCt4gS4AV_FAS2ynT4&rs=AOga4qnTBXb2uidyVhaajNfMb1GQZt_Cug
45783
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet.js
41114
https://www.googletagservices.com/activeview/js/current/rx_lidar.js?cache=r20110914
37234
https://pagead2.googlesyndication.com/pagead/show_ads.js
33487
https://www.medipedia.pt/templates/default/js/jquery-1.6.1.min.js
32360
Avoids an excessive DOM size — 524 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
524
Maximum DOM Depth
11
Maximum Child Elements
204
Avoid chaining critical requests — 34 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Medipedia.pt should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://googleads.g.doubleclick.net/pagead/ads?client=ca-pub-8046867249897342&output=html&h=90&slotname=8031613925&adk=3956361427&adf=813951275&pi=t.ma~as.8031613925&w=728&lmt=1618130359&url=https%3A%2F%2Fwww.medipedia.pt%2F&flash=0&wgl=1&dt=1618130359495&bpp=20&bdt=5725&idt=134&shv=r20210406&cbv=r20190131&ptt=5&saldr=sa&abxe=1&correlator=1767588049093&frm=20&pv=2&ga_vid=1085412387.1618130360&ga_sid=1618130360&ga_hid=1378306091&ga_fc=0&u_tz=-420&u_his=2&u_java=0&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_nplug=0&u_nmime=0&adx=176&ady=169&biw=1350&bih=940&scr_x=0&scr_y=0&eid=44740079%2C44739387&oid=3&pvsid=1616256539841695&pem=373&eae=0&fc=640&brdim=0%2C0%2C0%2C0%2C800%2C0%2C1%2C1%2C1350%2C940&vis=1&rsz=%7C%7ClE%7C&abl=CS&pfx=0&fu=0&bc=31&ifi=1&uci=a!1&fsb=1&xpc=Helk7lLNex&p=https%3A//www.medipedia.pt&dtd=165
181.224
150.845
6.472
https://tpc.googlesyndication.com/sodar/sodar2/222/runner.html
178.841
166.365
2.406
Unattributable
129.409
1.84
0.188
https://www.medipedia.pt/
124.38
4.096
2.87
https://www.googletagservices.com/activeview/js/current/osd.js?cb=%2Fr20100101
113.152
105.192
2.671
https://pagead2.googlesyndication.com/pagead/js/r20210406/r20190131/show_ads_impl_fy2019.js
59.499
49.253
6.257
https://www.googletagservices.com/activeview/js/current/rx_lidar.js?cache=r20110914
56.605
38.549
3.257
https://www.medipedia.pt/templates/default/js/jquery-1.6.1.min.js
52.631
36.123
2.361
Minimizes main-thread work — 1.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
746.30599999999
Other
183.072
Script Parsing & Compilation
93.058
Style & Layout
54.899
Parse HTML & CSS
49.46
Rendering
43.262
Garbage Collection
27.471
Keep request counts low and transfer sizes small — 101 requests • 1,376 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
101
1409000
Script
39
934240
Image
32
330078
Stylesheet
11
53627
Document
7
49556
Font
3
29080
Other
9
12419
Media
0
0
Third-party
42
504042
Minimize third-party usage — Third-party code blocked the main thread for 50 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
376119
48.162
69222
0
31609
0
19157
0
6742
0
1193
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0020804959066632
0.00049430577445057
0.00042241842512331
2.3148184630651E-5
1.9620499883256E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://pagead2.googlesyndication.com/bg/rg7ZOtwj_KsF30rM_Y0_DmvJrp5jy6rfjTYWIxfvKAc.js
1369
109
https://www.googletagservices.com/activeview/js/current/rx_lidar.js?cache=r20110914
3354
60
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Time to Interactive — 2.6 s
The time taken for the page to become fully interactive.

Opportunities

Serve images in next-gen formats — Potential savings of 200 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.medipedia.pt/templates/default/images/v2/front_medicos.png
168816
151658
https://tpc.googlesyndication.com/simgad/3591994845642353856?sqp=4sqPyQQ7QjkqNxABHQAAtEIgASgBMAk4A0DwkwlYAWBfcAKAAQGIAQGdAQAAgD-oAQGwAYCt4gS4AV_FAS2ynT4&rs=AOga4qnTBXb2uidyVhaajNfMb1GQZt_Cug
45189
34017
https://www.medipedia.pt/templates/default/images/v2/facebook_banner.png
22073
19071
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Medipedia.pt should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://medipedia.pt/
190
https://medipedia.pt/
150
https://www.medipedia.pt/
0

Diagnostics

Serve static assets with an efficient cache policy — 44 resources found
Medipedia.pt can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://connect.facebook.net/pt_PT/sdk.js
1200000
2685
https://ssl.google-analytics.com/ga.js
7200000
17798
https://www.medipedia.pt/templates/default/js/jquery-1.6.1.min.js
604800000
32360
https://www.medipedia.pt/templates/default/css/style_v2.css
604800000
24709
https://www.medipedia.pt/templates/default/js/qtip/jquery.qtip.js
604800000
15848
https://www.medipedia.pt/templates/default/leafletmaps/css/all.css
604800000
12807
https://static.getclicky.com/js
604800000
6156
https://www.medipedia.pt/templates/default/js/fancybox/jquery.fancybox-1.3.1.js
604800000
5505
https://www.medipedia.pt/templates/default/leafletmaps/css/leaflet.css
604800000
3705
https://www.medipedia.pt/templates/default/css/jQueryThemes/start/jquery-ui-json-suggest_v2.css
604800000
3028
https://www.medipedia.pt/templates/default/js/qtip/jquery.qtip.css
604800000
2617
https://www.medipedia.pt/templates/default/js/jquery.jsonSuggest_pesquisa.js
604800000
2199
https://www.medipedia.pt/templates/default/js/fancybox/jquery.fancybox-1.3.1.css
604800000
1597
https://www.medipedia.pt/templates/default/js/jquery.session.js
604800000
1131
https://www.medipedia.pt/templates/default/leafletmaps/css/leaflet.awesome-markers.css
604800000
1053
https://www.medipedia.pt/templates/default/js/Nibbler.min.js
604800000
983
https://www.medipedia.pt/templates/default/leafletmaps/handling/leaflet-gesture-handling.css
604800000
874
https://www.medipedia.pt/templates/default/js/inicio.js
604800000
833
https://www.medipedia.pt/templates/default/leafletmaps/css/mapstyle.css
604800000
708
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/client/one_click_handler_one_afma_fy2019.js
1209600000
11260
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/abg_lite_fy2019.js
1209600000
7895
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/client/qs_click_protection_fy2019.js
1209600000
6379
https://tpc.googlesyndication.com/pagead/js/r20210406/r20110914/client/window_focus_fy2019.js
1209600000
2084
https://www.medipedia.pt/templates/default/images/v2/front_medicos.png
2592000000
169196
https://www.medipedia.pt/home/components/images/spotimages/2.jpg
2592000000
26550
https://www.medipedia.pt/templates/default/images/v2/facebook_banner.png
2592000000
22451
https://www.medipedia.pt/templates/default/images/v2/novidade-submit.png
2592000000
3316
https://www.medipedia.pt/templates/default/images/v2/seta_todos.png
2592000000
3259
https://www.medipedia.pt/templates/default/images/v2/logotipo.png
2592000000
3106
https://www.medipedia.pt/templates/default/images/v2/marqueconsulta-submit.png
2592000000
2120
https://www.medipedia.pt/templates/default/images/v2/box_1.png
2592000000
1835
https://www.medipedia.pt/templates/default/images/v2/box_3.png
2592000000
1757
https://www.medipedia.pt/templates/default/images/v2/box_2.png
2592000000
1730
https://www.medipedia.pt/templates/default/images/v2/anf.png
2592000000
978
https://www.medipedia.pt/templates/default/images/v2/background.png
2592000000
821
https://www.medipedia.pt/templates/default/images/v2/i2_google.png
2592000000
736
https://www.medipedia.pt/templates/default/images/v2/i2_tweeter.png
2592000000
714
https://www.medipedia.pt/templates/default/images/v2/i2_facebook.png
2592000000
701
https://www.medipedia.pt/templates/default/images/v2/interrogacao_redondo.png
2592000000
642
https://www.medipedia.pt/templates/default/images/v2/bt_pesquisa.png
2592000000
637
https://www.medipedia.pt/templates/default/images/v2/farmacias-submit.png
2592000000
624
https://www.medipedia.pt/templates/default/images/v2/barra_separadora.png
2592000000
512
https://www.medipedia.pt/templates/default/images/v2/barra_separadora_cat.png
2592000000
488
https://www.medipedia.pt/templates/default/images/v2/barra_separadora_in.png
2592000000
480

Metrics

First Contentful Paint — 2.3 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 6.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.4 s
The timing of the largest text or image that is painted.

Other

First Meaningful Paint — 2.3 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 2,400 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Medipedia.pt should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.medipedia.pt/templates/default/css/style_v2.css
24709
190
https://www.medipedia.pt/templates/default/js/fancybox/jquery.fancybox-1.3.1.css
1597
150
https://www.medipedia.pt/templates/default/js/qtip/jquery.qtip.css
2617
150
https://fonts.googleapis.com/css?family=Open+Sans:400,600,800,700
1462
230
https://www.medipedia.pt/templates/default/css/jQueryThemes/start/jquery-ui-json-suggest_v2.css
3028
150
https://www.medipedia.pt/templates/default/leafletmaps/css/mapstyle.css
708
150
https://www.medipedia.pt/templates/default/leafletmaps/css/leaflet.css
3705
150
https://www.medipedia.pt/templates/default/leafletmaps/css/all.css
12807
110
https://www.medipedia.pt/templates/default/leafletmaps/css/leaflet.awesome-markers.css
1053
70
https://www.medipedia.pt/templates/default/leafletmaps/handling/leaflet-gesture-handling.css
874
70
https://www.medipedia.pt/templates/default/js/jquery-1.6.1.min.js
32360
230
https://www.medipedia.pt/templates/default/js/geral.js
3604
70
https://www.medipedia.pt/templates/default/js/pesquisa_solr.js
5329
70
https://www.medipedia.pt/templates/default/js/fancybox/jquery.fancybox-1.3.1.js
5505
70
https://www.medipedia.pt/templates/default/js/qtip/jquery.qtip.js
15848
150
https://www.medipedia.pt/templates/default/js/jquery.session.js
1131
70
https://www.medipedia.pt/templates/default/js/Nibbler.min.js
983
70
https://www.medipedia.pt/templates/default/js/facebook.js?1618130353
1478
70
https://www.medipedia.pt/templates/default/js/jquery.jsonSuggest_pesquisa.js
2199
70
https://www.medipedia.pt/templates/default/js/farmacia.js
1455
70
https://www.medipedia.pt/templates/default/js/pesquisar.js
7164
110
https://www.medipedia.pt/templates/default/js/inicio.js
833
70
https://www.medipedia.pt/templates/default/leafletmaps/js/MapManager.js
3769
70
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet.js
41114
230
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet-providers.js
6902
70
https://www.medipedia.pt/templates/default/leafletmaps/js/all.js
415106
550
https://www.medipedia.pt/templates/default/leafletmaps/js/leaflet.awesome-markers.js
2006
70
https://www.medipedia.pt/templates/default/leafletmaps/handling/leaflet-gesture-handling.js
8232
110
https://www.medipedia.pt/templates/default/js/google.js
2585
70
Reduce initial server response time — Root document took 1,250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.medipedia.pt/
1245.761

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
3.6209999816492
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
3.8770000101067
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
3.2009999849834
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.medipedia.pt/home/components/images/spotimages/2.jpg
img
https://www.medipedia.pt/templates/default/images/v2/i2_google.png
img
https://www.medipedia.pt/templates/default/images/v2/i2_tweeter.png
img
https://www.medipedia.pt/templates/default/images/v2/i2_facebook.png
img
58

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of medipedia.pt. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Medipedia.pt may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
`<input type="image">` elements do not have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
73

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that medipedia.pt should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.6.1
Leaflet
1.4.0+HEAD.3337f36
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://medipedia.pt/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 7 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
7
Medium

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Registers an `unload` listener
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Source
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.medipedia.pt/templates/default/leafletmaps/js/all.js
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for medipedia.pt. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of medipedia.pt on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
11
https://www.medipedia.pt/sitemap.xml.gz # Added by Google Sitemap Generator
Unknown directive

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
36

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of medipedia.pt. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of medipedia.pt on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 59
Performance 40
Accessibility 59
Best Practices 80
SEO 72
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.medipedia.pt
Updated: 11th April, 2021

3.17 seconds
First Contentful Paint (FCP)
14%
58%
28%

0.15 seconds
First Input Delay (FID)
73%
22%
5%

Simulate loading on mobile
40

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for medipedia.pt. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 40 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.001
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive medipedia.pt as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://medipedia.pt/
http/1.1
0
409.42399995402
384
0
302
text/html
https://medipedia.pt/
http/1.1
410.14800034463
1207.6710001566
413
0
301
text/html
https://www.medipedia.pt/
http/1.1
1208.3490001969
2026.0530002415
437
0
302
text/html
http://www.medipedia.pt/mobile/
http/1.1
2026.7270002514
2224.7210000642
394
0
302
text/html
https://www.medipedia.pt/mobile/
http/1.1
2225.479000248
3316.8979999609
10790
45778
200
text/html
Document
https://fonts.googleapis.com/css?family=Open+Sans:400,300,700,600
h2
3333.5490003228
3348.8950002939
1467
8424
200
text/css
Stylesheet
https://netdna.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css
h2
3333.7660003453
3368.0600002408
17983
109518
200
text/css
Stylesheet
https://netdna.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css
h2
3334.2980002053
3389.85399995
6306
23739
200
text/css
Stylesheet
https://www.medipedia.pt/mobile/templates/default/css/css.php
http/1.1
3334.5650001429
4132.5840000063
9166
45040
200
text/css
Stylesheet
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/MapManager.js
http/1.1
3334.8090001382
3837.7930000424
3743
15588
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.js
http/1.1
3335.0070002489
5645.1469999738
41089
141125
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet-providers.js
http/1.1
3335.4080002755
4148.2350002043
6877
22850
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/all.js
http/1.1
3335.683000274
4659.3140000477
415082
1174322
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.awesome-markers.js
http/1.1
3335.8370000497
4124.8090001754
1982
6241
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/leafletmaps/handling/leaflet-gesture-handling.js
http/1.1
3336.1410000362
4765.5340000056
8207
35680
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/css/medipediapt/jQueryThemes/start/jquery-ui-json-suggest_v2.css
http/1.1
3336.3330001011
4139.46700003
4181
19248
200
text/css
Stylesheet
https://code.jquery.com/jquery-1.11.0.min.js
h2
3336.622999981
3358.6099999957
33809
96381
200
application/javascript
Script
https://netdna.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js
h2
3336.8180003017
3435.5160002597
9389
31819
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/js/bootstrap-multiselect.js
http/1.1
3337.1399999596
4229.4880002737
11116
54619
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/js/jquery.sidr.min.js
http/1.1
3337.3320000246
3831.5360001288
2085
3673
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/js/custom.js
http/1.1
3337.7740001306
5441.2050000392
2447
7877
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/js/medipediapt/pesquisa_solr_medico.js
http/1.1
3337.9720002413
4133.3779999986
4422
12590
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/js/medipediapt/pesquisar.js
http/1.1
3338.2930001244
4432.696999982
6340
34565
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/js/medipediapt/jquery.jsonSuggest_pesquisa.js
http/1.1
3338.4830001742
4151.252000127
5050
13715
200
application/javascript
Script
https://www.medipedia.pt/mobile/templates/default/images/icon/menu-back.png
http/1.1
5723.1070003472
6213.3460002951
541
169
200
image/png
Image
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
h2
5725.848000031
5729.2740000412
9695
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
h2
5728.5070000216
5731.2779999338
9743
9180
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
h2
5728.7010001019
5731.7730002105
9643
9080
200
font/woff2
Font
https://www.medipedia.pt/mobile/templates/default/images/header-logo.svg
http/1.1
5802.2960000671
6506.1880000867
3765
3466
200
image/svg+xml
Document
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
3349.352
8.68
3361.302
6.006
3398.442
5.374
5682.453
61.301
5743.773
23.37
5767.44
55.797
6537.53
7.641
6547.301
6.047
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Medipedia.pt should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Medipedia.pt should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Medipedia.pt should consider minifying CSS files.
Minify JavaScript — Potential savings of 13 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Medipedia.pt should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.medipedia.pt/mobile/templates/default/js/bootstrap-multiselect.js
11116
6260
https://www.medipedia.pt/mobile/templates/default/js/medipediapt/jquery.jsonSuggest_pesquisa.js
5050
2850
https://www.medipedia.pt/mobile/templates/default/js/medipediapt/pesquisar.js
6340
2334
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/MapManager.js
3743
2200
Remove unused CSS — Potential savings of 17 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Medipedia.pt should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://netdna.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css
17983
17175
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Medipedia.pt should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.js
6276
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/all.js
59
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 622 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/all.js
415082
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.js
41089
https://code.jquery.com/jquery-1.11.0.min.js
33809
https://netdna.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css
17983
https://www.medipedia.pt/mobile/templates/default/js/bootstrap-multiselect.js
11116
https://www.medipedia.pt/mobile/
10790
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
9743
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
9695
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
9643
https://netdna.bootstrapcdn.com/bootstrap/3.2.0/js/bootstrap.min.js
9389
Uses efficient cache policy on static assets — 3 resources found
Medipedia.pt can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.medipedia.pt/mobile/templates/default/css/medipediapt/jQueryThemes/start/jquery-ui-json-suggest_v2.css
604800000
4181
https://www.medipedia.pt/mobile/templates/default/images/icon/menu-back.png
2592000000
541
https://www.medipedia.pt/mobile/templates/default/css/css.php
2678383000
9166
Avoids an excessive DOM size — 531 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
531
Maximum DOM Depth
01
11
Maximum Child Elements
204
Avoid chaining critical requests — 21 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Medipedia.pt should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.medipedia.pt/mobile/
263.568
16.08
9.284
https://code.jquery.com/jquery-1.11.0.min.js
152.336
129.28
9.368
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/all.js
151.268
62.544
78.456
Unattributable
136.424
4.804
0.724
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.js
64.26
49.12
10.576
Minimizes main-thread work — 0.9 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
290.14
Other
208.656
Script Parsing & Compilation
144.76
Parse HTML & CSS
122.824
Style & Layout
120.248
Rendering
19.988
Keep request counts low and transfer sizes small — 29 requests • 622 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
636546
Script
14
551638
Stylesheet
5
39103
Font
3
29081
Document
2
14555
Other
4
1628
Image
1
541
Media
0
0
Third-party
8
98035
Minimize third-party usage — Third-party code blocked the main thread for 20 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
33809
18.444
33678
0
30548
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 4 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0004206657409668
0.00013656764560276
0.00011897616916233
0.00010729100969103
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 2 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.js
6840
245
https://code.jquery.com/jquery-1.11.0.min.js
7920
112
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Opportunities

Remove unused JavaScript — Potential savings of 34 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.js
41089
34396

Metrics

First Contentful Paint — 7.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 13.1 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 7.5 s
The timing of the largest text or image that is painted.
Time to Interactive — 7.5 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 7.5 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 7.5 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 15321.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 4,380 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Medipedia.pt should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Open+Sans:400,300,700,600
1467
780
https://netdna.bootstrapcdn.com/bootstrap/3.2.0/css/bootstrap.min.css
17983
1530
https://netdna.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css
6306
300
https://www.medipedia.pt/mobile/templates/default/css/css.php
9166
480
https://www.medipedia.pt/mobile/templates/default/css/medipediapt/jQueryThemes/start/jquery-ui-json-suggest_v2.css
4181
480
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/MapManager.js
3743
630
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.js
41089
1980
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet-providers.js
6877
780
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/all.js
415082
4230
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/leaflet.awesome-markers.js
1982
180
https://www.medipedia.pt/mobile/templates/default/leafletmaps/handling/leaflet-gesture-handling.js
8207
480
Reduce initial server response time — Root document took 1,090 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.medipedia.pt/mobile/
1092.415
Avoid multiple page redirects — Potential savings of 2,220 ms
Redirects can cause additional delays before the page can begin loading. Medipedia.pt should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://medipedia.pt/
630
https://medipedia.pt/
480
https://www.medipedia.pt/
780
http://www.medipedia.pt/mobile/
330
https://www.medipedia.pt/mobile/
0

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
3.4260000102222
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
2.7709999121726
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
3.0720001086593
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
59

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of medipedia.pt. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Medipedia.pt may provide assistance to deaf or hearing-impaired users with captions on videos.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
 
Document doesn't have a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements do not have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.
Failing Elements

Contrast

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that medipedia.pt should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.2.0
jQuery
1.11.0
Leaflet
1.4.0+HEAD.3337f36
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 2 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://medipedia.pt/
Allowed
http://www.medipedia.pt/mobile/
Allowed
Requests the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Source
Includes front-end JavaScript libraries with known security vulnerabilities — 9 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
5
Medium
4
Medium

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.medipedia.pt/mobile/templates/default/leafletmaps/js/all.js
72

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for medipedia.pt. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of medipedia.pt on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Mobile Friendly

Tap targets are not sized appropriately — 75% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
140x22

Content Best Practices

Document doesn't have a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Failing Elements
Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — 1 error found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
11
https://www.medipedia.pt/sitemap.xml.gz # Added by Google Sitemap Generator
Unknown directive

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
42

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of medipedia.pt. This includes details about web app manifests.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of medipedia.pt on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 5.79.97.201
Continent: Europe
Country: Netherlands
Netherlands Flag
Region:
City:
Longitude: 4.8995
Latitude: 52.3824
Currencies: EUR
Languages: Dutch

Web Hosting Provider

Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 3.5/5 (0 reviews)
WOT Trustworthiness: 70/100
WOT Child Safety: 79/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: medipedia.pt
Issued By: R3
Valid From: 14th February, 2021
Valid To: 15th May, 2021
Subject: CN = medipedia.pt
Hash: 4ac2a323
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04A8766E7277828FBAD35B98A1FC8BFA9AA5
Serial Number (Hex): 04A8766E7277828FBAD35B98A1FC8BFA9AA5
Valid From: 14th February, 2024
Valid To: 15th May, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
Timestamp : Feb 14 17:15:49.305 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:96:48:99:BE:29:CB:A9:A2:93:4A:44:
69:F7:52:54:2B:10:31:B2:9C:91:73:04:64:11:A3:24:
84:B1:56:8D:54:02:21:00:CB:B0:6E:CD:21:AF:2E:C2:
EB:8B:1B:DE:CE:AE:5B:29:1B:10:92:CD:5D:75:70:50:
5D:49:7A:AD:EA:4D:F8:9C
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Feb 14 17:15:49.280 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:73:FA:C5:97:80:EA:B1:3B:56:51:26:72:
7D:CE:E1:21:1B:5B:A6:38:F0:BF:0B:A9:18:7D:68:30:
1B:93:D3:D8:02:21:00:8D:46:5B:8E:64:8E:7A:21:61:
56:89:13:EB:59:6A:87:1C:D4:66:6F:00:5C:D3:8C:B1:
44:2E:E7:C1:26:AB:42
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:medipedia.pt
DNS:wmc.medipedia.pt
DNS:www.medipedia.com.br
DNS:www.medipedia.pt
DNS:medipedia.com.br
Technical

DNS Lookup

A Records

Host IP Address Class TTL
medipedia.pt. 5.79.97.201 IN 21599

NS Records

Host Nameserver Class TTL
medipedia.pt. ns17.hostedbymagicbrain.com. IN 21599
medipedia.pt. ns9.hostedbymagicbrain.com. IN 21599
medipedia.pt. ns11.hostedbymagicbrain.com. IN 21599
medipedia.pt. ns15.hostedbymagicbrain.com. IN 21599

MX Records

Priority Host Server Class TTL
0 medipedia.pt. aspmx.l.google.com. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
medipedia.pt. ns9.hostedbymagicbrain.com. support.magic4hosting.com. 21599

TXT Records

Host Value Class TTL
medipedia.pt. v=spf1 IN 21599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 11th April, 2021
Server: Apache/2.2.22
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Content-Type: text/html; charset=ISO-8859-1
X-Powered-By: PHP/5.3.10-1ubuntu3.21
Set-Cookie: *
Pragma: no-cache
Connection: keep-alive
Vary: Accept-Encoding

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns11.hostedbymagicbrain.com
ns15.hostedbymagicbrain.com
ns17.hostedbymagicbrain.com
ns9.hostedbymagicbrain.com
Full Whois:

Nameservers

Name IP Address
ns11.hostedbymagicbrain.com 37.58.59.226
ns15.hostedbymagicbrain.com 185.173.32.32
ns17.hostedbymagicbrain.com 185.173.32.120
ns9.hostedbymagicbrain.com 37.58.59.225
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$7,489 USD 2/5
0/5
0/5

Sites hosted on the same IP address