22.3 sec in total
18 ms
21.4 sec
880 ms
Click here to check amazing Pavilhaosaosebastiao Wordpress content for United States. Otherwise, check out these important facts you probably never knew about pavilhaosaosebastiao.wordpress.com
Bem-vindos ao Pavilhão São Sebastião. Situado no centro histórico de Sintra, num espaço privilegiado pela natureza. Proporcionamos aqueles que procuram estar em sintonia com o universo interior e exte...
Visit pavilhaosaosebastiao.wordpress.comWe analyzed Pavilhaosaosebastiao.wordpress.com page load time and found that the first response time was 18 ms and then it took 22.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
pavilhaosaosebastiao.wordpress.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value5.9 s
14/100
25%
Value7.2 s
30/100
10%
Value26,700 ms
0/100
30%
Value0.118
85/100
15%
Value39.4 s
0/100
10%
18 ms
289 ms
58 ms
67 ms
61 ms
Our browser made a total of 218 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Pavilhaosaosebastiao.wordpress.com, 10% (22 requests) were made to S.pubmine.com and 8% (18 requests) were made to Usersync.gumgum.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Ssl-market-east.smrtb.com.
Page size can be reduced by 58.7 kB (30%)
193.6 kB
134.9 kB
In fact, the total size of Pavilhaosaosebastiao.wordpress.com main page is 193.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. HTML takes 72.4 kB which makes up the majority of the site volume.
Potential reduce by 52.9 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 52.9 kB or 73% of the original size.
Potential reduce by 4 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Pavilhaosaosebastiao Wordpress images are well optimized though.
Potential reduce by 5.6 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 5.6 kB or 12% of the original size.
Potential reduce by 209 B
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Pavilhaosaosebastiao.wordpress.com has all CSS files already compressed.
Number of requests can be reduced by 139 (79%)
175
36
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pavilhaosaosebastiao Wordpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pavilhaosaosebastiao.wordpress.com
18 ms
pavilhaosaosebastiao.wordpress.com
289 ms
wp-emoji-release.min.js
58 ms
67 ms
style.css
61 ms
css
73 ms
57 ms
63 ms
66 ms
71 ms
70 ms
w.js
70 ms
conf
123 ms
ga.js
72 ms
pavilhaos_sbestiao_backgound_2.jpg
136 ms
wpcom-gray-white.png
63 ms
g.gif
69 ms
74 ms
g.gif
63 ms
g.gif
65 ms
pavilhao_logo2.jpg
188 ms
cropped-image005.jpg
73 ms
caetanajanela2.jpg
47 ms
SlGVmQWMvZQIdix7AFxXkHNSaA.ttf
73 ms
SlGWmQWMvZQIdix7AFxXmMh3eDs1Yg.ttf
76 ms
tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf
86 ms
tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf
87 ms
tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf
88 ms
tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf
184 ms
__utm.gif
28 ms
ata.js
27 ms
5.js
51 ms
pixel
48 ms
tag.js
204 ms
uc.html
380 ms
user_sync.html
426 ms
user_sync.html
577 ms
d
658 ms
prbds2s
569 ms
async_usersync.html
543 ms
user_sync.html
567 ms
usync.html
649 ms
checksync.php
647 ms
iframe
407 ms
jslog
157 ms
jslog
237 ms
match
157 ms
all
20321 ms
match
481 ms
30907
750 ms
setuid
452 ms
sync
227 ms
match
225 ms
PugMaster
758 ms
usermatch
229 ms
URnmbSKM
733 ms
user_sync.html
345 ms
match
190 ms
match
182 ms
match
161 ms
pd
282 ms
match
359 ms
ix
590 ms
pixel
667 ms
match
351 ms
usersync.aspx
811 ms
cksync.php
369 ms
884 ms
937 ms
match
296 ms
match
454 ms
match
454 ms
usync.js
348 ms
match
367 ms
getuid
589 ms
0.gif
875 ms
match
243 ms
match
308 ms
us.gif
241 ms
usersync
719 ms
167a190f-92aa-e97f-c478-f47e20c83e75
577 ms
ny75r2x0
511 ms
getuid
455 ms
us.gif
233 ms
us.gif
436 ms
cksync.php
312 ms
demconf.jpg
313 ms
pixel
404 ms
engine
686 ms
us.gif
309 ms
cksync.php
442 ms
match
206 ms
usersync
482 ms
cksync.php
482 ms
us.gif
274 ms
rubicon
331 ms
pixel
266 ms
pixel
297 ms
info2
285 ms
b9pj45k4
367 ms
match
278 ms
0EF9C55A-0EA0-4265-89DA-94936FA1B6C3
276 ms
generic
313 ms
us.gif
306 ms
usersync
509 ms
pixel
353 ms
usersync
471 ms
cksync.html
359 ms
usersync
468 ms
usersync
464 ms
rum
316 ms
usersync
437 ms
usersync
417 ms
usync.html
213 ms
usersync
467 ms
us.gif
170 ms
us.gif
209 ms
cs&eq_cc=1
144 ms
rtset
165 ms
usg.gif
213 ms
tap.php
212 ms
dcm
209 ms
usync.html
298 ms
cksync
361 ms
us.gif
155 ms
tap.php
284 ms
rum
227 ms
usersync
350 ms
user_sync.html
214 ms
Pug
431 ms
1000.gif
207 ms
crum
249 ms
Pug
423 ms
usersync
328 ms
Pug
372 ms
rum
276 ms
Pug
363 ms
usersync
286 ms
sd
193 ms
cksync
384 ms
usermatchredir
178 ms
sd
173 ms
cksync.php
168 ms
crum
207 ms
usersync
191 ms
pixel
137 ms
match
136 ms
usync.html
128 ms
cksync.php
192 ms
Pug
216 ms
sync
102 ms
cksync.php
120 ms
sd
119 ms
Pug
184 ms
pixel
91 ms
cksync.php
171 ms
pixel
95 ms
match
89 ms
match
90 ms
usersync
83 ms
ecm3
93 ms
tap.php
81 ms
usersync
78 ms
match
178 ms
match
159 ms
usersync
76 ms
cksync.php
105 ms
match
113 ms
match
107 ms
31 ms
match
50 ms
28 ms
cksync.php
40 ms
usersync
17 ms
cksync.php
48 ms
cksync.php
61 ms
10 ms
match
6 ms
match
6 ms
ecm3
74 ms
PugMaster
36 ms
PugMaster
41 ms
p.gif
124 ms
info
72 ms
g.pixel
90 ms
generic
12 ms
usersync.aspx
59 ms
sn.ashx
190 ms
match
55 ms
Pug
59 ms
Pug
43 ms
Pug
22 ms
Pug
13 ms
Pug
16 ms
p.gif
32 ms
Pug
12 ms
Pug
13 ms
Artemis
43 ms
sn.ashx
38 ms
PugMaster
11 ms
sync
7 ms
pubmatic
86 ms
i.match
145 ms
usersync
33 ms
Pug
32 ms
Pug
43 ms
Pug
30 ms
pixel
15 ms
qmap
48 ms
Pug
15 ms
Pug
20 ms
pbmtc.gif
12 ms
generic
11 ms
receive
19 ms
Pug
12 ms
i.match
114 ms
Pug
13 ms
725X1342.skimlinks.js
40 ms
pavilhaosaosebastiao.wordpress.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
pavilhaosaosebastiao.wordpress.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pavilhaosaosebastiao.wordpress.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pavilhaosaosebastiao.wordpress.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Pavilhaosaosebastiao.wordpress.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
pavilhaosaosebastiao.wordpress.com
Open Graph data is detected on the main page of Pavilhaosaosebastiao Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: