4.9 sec in total
187 ms
4.6 sec
102 ms
Welcome to potrerowar.org homepage info - get ready to check Potrero War best content right away, or after learning these important things about potrerowar.org
LIGA2000 mengulas atmosfer perkemahan sejarah, demonstrasi kerajinan antik, serta persahabatan antar-komunitas dalam ajang Potrero War.
Visit potrerowar.orgWe analyzed Potrerowar.org page load time and found that the first response time was 187 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
potrerowar.org performance score
name
value
score
weighting
Value11.9 s
0/100
10%
Value11.9 s
0/100
25%
Value11.9 s
4/100
10%
Value1,100 ms
23/100
30%
Value0.012
100/100
15%
Value16.5 s
5/100
10%
187 ms
317 ms
431 ms
29 ms
37 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Potrerowar.org, 39% (38 requests) were made to Places.sca-caid.org and 23% (22 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Places.sca-caid.org.
Page size can be reduced by 230.8 kB (3%)
6.8 MB
6.6 MB
In fact, the total size of Potrerowar.org main page is 6.8 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. Images take 6.1 MB which makes up the majority of the site volume.
Potential reduce by 154.8 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 154.8 kB or 84% of the original size.
Potential reduce by 68.9 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. Potrero War images are well optimized though.
Potential reduce by 4.7 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.3 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. Potrerowar.org needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 17% of the original size.
Number of requests can be reduced by 55 (70%)
79
24
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potrero War. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
potrerowar.org
187 ms
www.potrerowar.org
317 ms
431 ms
jquery.dataTables.min.css
29 ms
buttons.dataTables.min.css
37 ms
select.dataTables.min.css
50 ms
fixedHeader.dataTables.min.css
54 ms
fixedColumns.dataTables.min.css
50 ms
responsive.dataTables.min.css
49 ms
owmweather.min.css
139 ms
wp-forecast-default.css
140 ms
css
36 ms
jquery.min.js
150 ms
jquery-migrate.min.js
135 ms
jquery.dataTables.min.js
13 ms
dataTables.buttons.min.js
13 ms
buttons.colVis.min.js
19 ms
buttons.print.min.js
28 ms
pdfmake.min.js
31 ms
vfs_fonts.js
52 ms
jszip.min.js
46 ms
buttons.html5.min.js
38 ms
dataTables.select.min.js
14 ms
dataTables.fixedHeader.min.js
15 ms
dataTables.fixedColumns.min.js
15 ms
dataTables.responsive.min.js
23 ms
igsv-datatables.js
139 ms
jsapi
15 ms
igsv-gvizcharts.js
138 ms
js
64 ms
et-core-unified-50.min.css
142 ms
owm-weather-ajax.js
142 ms
register-sw.js
2040 ms
scripts.min.js
2042 ms
smoothscroll.js
2040 ms
magnific-popup.js
2041 ms
salvattore.js
2041 ms
common.js
2041 ms
loader.js
22 ms
buttons.colVis.min.js
13 ms
buttons.print.min.js
14 ms
buttons.html5.min.js
15 ms
loader.js
18 ms
Potrero-War-Logo-2.png
354 ms
285067137_10158440418206594_1377883063634023036_n.jpg
485 ms
photo-by-Emil-Camus-2.jpg
429 ms
photo-by-Cesar-Alejandro-de-Baracoa-5-e1706914036230.jpg
340 ms
photo-by-Emil-Camus-6-e1706914018433.jpg
423 ms
photo-by-Emil-Camus-1-e1706913946760.jpg
420 ms
photo-by-Cesar-Alejandro-de-Baracoa-3-e1706914125699.jpg
409 ms
Warphoto2.jpg
635 ms
photo-by-Cesar-Alejandro-de-Baracoa-8-e1706914533801.jpg
476 ms
photo-by-Cesar-Alejandro-de-Baracoa-2-e1706914175743.jpg
490 ms
photo-by-Emil-Camus-8-e1706913978726.jpg
494 ms
photo-by-Emil-Camus-7-e1706914004545.jpg
501 ms
photo-by-Cesar-Alejandro-de-Baracoa-10-e1706914445216.jpg
544 ms
photo-by-Emil-Camus-10-e1706913963597.jpg
555 ms
photo-by-Cesar-Alejandro-de-Baracoa-15-e1706914151537.jpg
561 ms
photo-by-Emil-Camus-3-e1706913908978.jpg
566 ms
photo-by-Cesar-Alejandro-de-Baracoa-13-e1706914369533.jpg
575 ms
photo-by-Cesar-Alejandro-de-Baracoa-12.jpg
617 ms
campfire-150x150.png
624 ms
court-150x150.jpg
631 ms
Map-Website-2020-150x150.jpg
636 ms
coronets-150x150.jpg
646 ms
et-divi-dynamic-50-late.css
637 ms
EvOJzAlL3oU5AQl2mP5KdgptMqZwNw.ttf
348 ms
2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZRekVh-sC.ttf
351 ms
2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZIukVh-sC.ttf
382 ms
2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZfOkVh-sC.ttf
384 ms
2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZkO4Vh-sC.ttf
360 ms
2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZou4Vh-sC.ttf
359 ms
2-cO9IRs1JiJN1FRAMjTN5zd9vgsFF_5asQTb6hZ2JKZ_O4Vh-sC.ttf
359 ms
u-4n0qyriQwlOrhSvowK_l52xwNZVsf_.ttf
357 ms
u-4n0qyriQwlOrhSvowK_l52_wFZVsf_.ttf
362 ms
u-440qyriQwlOrhSvowK_l5-ciZJ.ttf
362 ms
u-4n0qyriQwlOrhSvowK_l521wRZVsf_.ttf
363 ms
tooltip.css
19 ms
util.css
24 ms
controls.css
25 ms
table.css
26 ms
format.css
24 ms
annotationchart.css
25 ms
jsapi_compiled_default_module.js
29 ms
jsapi_compiled_graphics_module.js
45 ms
jsapi_compiled_ui_module.js
51 ms
jsapi_compiled_corechart_module.js
28 ms
jsapi_compiled_controls_module.js
45 ms
jsapi_compiled_table_module.js
44 ms
jsapi_compiled_annotationchart_module.js
48 ms
jsapi_compiled_annotatedtimeline_module.js
48 ms
jsapi_compiled_gauge_module.js
48 ms
jsapi_compiled_geo_module.js
48 ms
jsapi_compiled_geochart_module.js
48 ms
jsapi_compiled_fw_module.js
79 ms
dygraph-tickers-combined.js
79 ms
jsapi_compiled_timeline_module.js
79 ms
potrerowar.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
potrerowar.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
potrerowar.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Potrerowar.org 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 Potrerowar.org 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.
potrerowar.org
Open Graph description is not detected on the main page of Potrero War. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: