4.8 sec in total
318 ms
3.6 sec
951 ms
Click here to check amazing Sanjuanpuertorico content for United States. Otherwise, check out these important facts you probably never knew about sanjuanpuertorico.com
San Juan Puerto Rico - Travel Guide - Things to Do, Attractions, Hotels & Resorts, Beaches, Vacation Ideas, Cruise Guide, Walking Tours, Travel Tips & More.
Visit sanjuanpuertorico.comWe analyzed Sanjuanpuertorico.com page load time and found that the first response time was 318 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sanjuanpuertorico.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.4 s
68/100
25%
Value10.5 s
7/100
10%
Value1,110 ms
23/100
30%
Value0.018
100/100
15%
Value15.5 s
7/100
10%
318 ms
261 ms
195 ms
136 ms
293 ms
Our browser made a total of 190 requests to load all elements on the main page. We found that 17% of them (33 requests) were addressed to the original Sanjuanpuertorico.com, 7% (13 requests) were made to D2c3g8zasxphdx.cloudfront.net and 6% (11 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Encrypted-tbn3.gstatic.com.
Page size can be reduced by 1.6 MB (40%)
4.0 MB
2.4 MB
In fact, the total size of Sanjuanpuertorico.com main page is 4.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 221.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 221.9 kB or 77% of the original size.
Potential reduce by 18.2 kB
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. Sanjuanpuertorico images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 59% of the original size.
Potential reduce by 245.8 kB
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. Sanjuanpuertorico.com needs all CSS files to be minified and compressed as it can save up to 245.8 kB or 73% of the original size.
Number of requests can be reduced by 110 (69%)
159
49
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sanjuanpuertorico. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
sanjuanpuertorico.com
318 ms
jY7BEoIwDER_iFo9-EGZEiBaUicJIH9vKTjCwdFTNjt5m736GrSjkFhPPXF18dPANUorKU8Pqmjqg-rBz2cMRokhugnBOhSnKCMFdBBRNoQn3dYlNyWNlCP2oU3E5-p-u1CbI1ZnH4BHUE8c4lDjIgxbKSV0R5am7-0XdkN7QLgXaNMf5K_HWYxks2uS9Gvfg_MC.css
261 ms
M9TPSi0pSEzO1o_PzEvWT0_NSy3KTM7PK8bOBAA.css
195 ms
RYxRDoAgDEMvZIIeCcdUFDdDh15fgjH8vaavndzOdnk6HAE_D6MjL7eHW4qQRRW0GptmIw2MblCB6dlzFEqlGhWM1-y_9aOKFAPn9jMXRGHgBQ.css
136 ms
M9bPKixNLarUMYYydHMz04sSS1L1cjPzgIKlmfrJ-UVIvPLMlPTUEgS_IL84syQzPw8hkpuaV4rgJZaW5Cfn5xbkpELMBAA.js
293 ms
M9QvL81LSS1KL8oH0vqJxcWpJcX6WcX65Zkp6aklermZeQA.js
144 ms
js
78 ms
M9BPTswrSyzWz8xLzilNSS3WzyrWL8nILErRLUgsKqnUy83M0zHApig3PyW1KC-zqgikBAA.js
142 ms
general.min.js
201 ms
css
34 ms
adsbygoogle.js
5 ms
nmedianet.js
68 ms
WidgetService.aspx
25 ms
WidgetService.aspx
6 ms
pinit.js
19 ms
addthis_widget.js
9 ms
LYxBCoAwDAQ_ZAx9UiiLRmsqTbTft2BPwzLsJM6Zcq2nYsAcFizuCOe7PJsaHc6_n3otEvBYL7UlsUloNSnUIbGjkaO9mkFS0EZkvK37XB8.js
152 ms
devicepx-jetpack.js
59 ms
gprofiles.js
58 ms
M9TPSi0pSEzO1s_NTynNSS3WLy9IL8rPyNcxAbJ0U3OTUlP0cjPzAA.js
151 ms
jYpRDkAwEAUvJDaO1NiHrdbSbZXbE_5FMh-TzHTkkVfXzxSVS4CRTS6BHfP5qCxj01FVtSCMRM4M2cjfbAXpbKMWQ52A0EZZvt8h4Hjbj1fyLmwX.js
233 ms
e-201609.js
8 ms
wp-emoji-release.min.js
90 ms
image-7571771-10395956-1426537613000
6 ms
10395956-1448986970506
17 ms
san-juan-puerto-rico-901.jpg
633 ms
San-Juan-Puerto-Rico-11.png
229 ms
image-7571771-10542897-1444318792000
26 ms
image-7571771-11421936
28 ms
261234_original.jpg
216 ms
ir
27 ms
Cupeles-Puerto-Rico-Travel-Guides.jpg
401 ms
san-juan-capital-city-puerto-rico.jpg
371 ms
old-san-juan-puerto-rico-893.jpg
354 ms
san-juan-puerto-rico-ddd.jpg
418 ms
old-san-juan-puerto-rico-789.jpg
208 ms
san-juan-condado-puerto-rico-45.jpg
283 ms
old-san-juan-puerto-rico-45.jpg
284 ms
san-juan-puerto-rico-beaches-345.jpg
312 ms
san-juan-puerto-rico-color-26.jpg
315 ms
san-juan-things-to-do-puerto-rico-4678.jpg
381 ms
san-juan-puerto-rico-events-culture.jpg
383 ms
san-juan-puerto-rico-hotels-345.jpg
435 ms
san-juan-puerto-rico-restaurants.jpg
449 ms
loading.gif
471 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
48 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
71 ms
fontawesome-webfont.woff
694 ms
ca-pub-4673701865647097.js
197 ms
zrt_lookup.html
196 ms
show_ads_impl.js
82 ms
10542897-1444320026034
29 ms
11421936-1444767387511
48 ms
ads
479 ms
Genericons.svg
395 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
3 ms
osd.js
23 ms
ads
210 ms
ads
348 ms
px.gif
38 ms
px.gif
34 ms
bping.php
31 ms
fcmdynet.js
337 ms
ads
115 ms
checksync.php
95 ms
usermatch
17 ms
abg.js
56 ms
usermatch
39 ms
m_js_controller.js
69 ms
pixel
120 ms
VtYqOcAoJH4AAEUxQvAAAAGZ%26407
129 ms
gr
97 ms
usersync.aspx
120 ms
ecsync.php
123 ms
csync.php
173 ms
favicon
180 ms
s
57 ms
googlelogo_color_112x36dp.png
221 ms
nessie_icon_thin_arrow_big_white.png
61 ms
x_button_blue2.png
75 ms
rum
168 ms
pixel
170 ms
crum
146 ms
crum
143 ms
log.php
111 ms
css
199 ms
rum
241 ms
mediamain.html
583 ms
favicon
330 ms
rum
93 ms
WidgetiFrame.aspx
549 ms
result.html
180 ms
261234_original.jpg
54 ms
bping.php
54 ms
fcmdynet.js
371 ms
crum
52 ms
m
197 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
79 ms
favicon
177 ms
favicon
394 ms
favicon
1214 ms
favicon
247 ms
favicon
278 ms
favicon
1215 ms
favicon
1236 ms
favicon
378 ms
favicon
379 ms
favicon
245 ms
hcom-searchform-300-HCOM_PARTNERS-partners_hotels_com-partners_PARTNERS.css
133 ms
jquery.js
149 ms
hcom-lib-searchform2.js
130 ms
hcom-searchform2.js
241 ms
MVabO2jbLZ8M0pzO6jqg2fesZW2xOQ-xsNqO47m55DA.ttf
309 ms
crum
65 ms
logo_162x23.png
232 ms
sprite_onebrandqueryform.png
232 ms
mediamain.html
675 ms
WidgetiFrame.aspx
459 ms
analytics.js
83 ms
sdk.js
351 ms
StreetViewWidget.html
70 ms
ga.js
67 ms
pinit_main.js
64 ms
getlc.js
269 ms
nrr.js
266 ms
collect
224 ms
StreetViewWidget.css
211 ms
streetviewwidget.nocache.js
212 ms
hovercard.css
54 ms
services.css
132 ms
share
278 ms
g.gif
48 ms
count.json
118 ms
graph.facebook.com
274 ms
300lo.json
114 ms
g.gif
90 ms
g.gif
90 ms
standard.css
91 ms
collect
243 ms
AdChoices.png
95 ms
__utm.gif
199 ms
sh.7c7179124ea24ac6ba46caac.html
180 ms
__utm.gif
167 ms
__utm.gif
169 ms
__utm.gif
169 ms
StreetViewWidget.html
160 ms
9374CDF9D5A4F03EF767ACEC9FF1CDD8.cache.html
127 ms
g.gif
81 ms
__utm.gif
90 ms
__utm.gif
90 ms
__utm.gif
91 ms
1.cache.js
71 ms
172 ms
layers.648fb6c882fbeb98be27.js
70 ms
__utm.gif
115 ms
2.cache.js
92 ms
bql.php
75 ms
px.gif
186 ms
xd_arbiter.php
148 ms
xd_arbiter.php
658 ms
20.cache.js
35 ms
bql.php
8 ms
3.cache.js
27 ms
5.cache.js
10 ms
19.cache.js
70 ms
11.cache.js
307 ms
light-bottom.css
454 ms
jstag
427 ms
pixel
403 ms
activeview
187 ms
san-juan-puerto-rico-7.jpg
392 ms
puerto-rico-things-to-do-places-to-see.jpg
306 ms
san-juan-puerto-rico-92.jpg
359 ms
1
71 ms
sync
71 ms
i.js
72 ms
bqi.php
17 ms
acj
29 ms
cookie-consent-logo.png
349 ms
js
61 ms
pd
61 ms
e0e73b6b-fdef-d7b0-7322-b66e8f5b7a71
53 ms
openx
48 ms
pixel
53 ms
openx
24 ms
sd
30 ms
sd
54 ms
sd
44 ms
sd
54 ms
sd
28 ms
sanjuanpuertorico.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
sanjuanpuertorico.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
sanjuanpuertorico.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanjuanpuertorico.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Sanjuanpuertorico.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.
sanjuanpuertorico.com
Open Graph data is detected on the main page of Sanjuanpuertorico. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: