Your Website Score is
27 concejodeliberante.sanmartindelosandes.gov.ar Last Updated: 2 years
Success
70% of passed verification steps
Warning
15% of total warning
Errors
15% of total errors, require fast action
Share
Desktop
Mobile
Page Authority
Authority 34%
Domain Authority
Domain Authority 45%
Moz Rank
3.4/10
Bounce Rate
Rate 0%
charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
48 Characters
| CONCEJO DELIBERANTE DE SAN MARTÍN DE LOS ANDES
Meta Description
46 Characters
Concejo Deliberante de San Martín de los Andes
Effective URL
52 Characters
http://concejodeliberante.sanmartindelosandes.gov.ar
Excerpt
Page content
| Concejo Deliberante de San Martín de los Andes
Concejo Delib...
Google Preview
Your look like this in google search result
| CONCEJO DELIBERANTE DE SAN MARTÍN DE LOS ANDES
http://concejodeliberante.sanmartindelosandes.gov.ar
Concejo Deliberante de San Martín de los Andes
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~56.49 KB
Code Size: ~37.36 KB
Text Size: ~19.13 KB Ratio: 33.87%
Social Data
Estimation Traffic and Earnings
8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly
Desktop
Serve static assets with an efficient cache policy
49 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint
8.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Network Round Trip Times
80 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Avoid chaining critical requests
23 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Minimizes main-thread work
1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index
9.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page
First Meaningful Paint
5.3 s
First Meaningful Paint measures when the primary content of a page is visible
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Total Blocking Time
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused JavaScript
Potential savings of 526 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Enable text compression
Potential savings of 480 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Server Backend Latencies
270 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Max Potential First Input Delay
40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids enormous network payloads
Total size was 2,074 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve images in next-gen formats
Potential savings of 75 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Cumulative Layout Shift
0.317
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce unused CSS
Potential savings of 636 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Properly size images
Potential savings of 102 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
JavaScript execution time
1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce initial server response time
Root document took 610 ms
Keep the server response time for the main document short because all other requests depend on it
Minify CSS
Potential savings of 72 KiB
Minifying CSS files can reduce network payload sizes
Avoids an excessive DOM size
518 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
Avoid long main-thread tasks
7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint
5.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid non-composited animations
7 animated elements found
Animations which are not composited can be janky and increase CLS
Minimize third-party usage
Third-party code blocked the main thread for 140 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Does not use HTTPS
58 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Eliminate render-blocking resources
Potential savings of 6,880 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify JavaScript
Potential savings of 47 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Time to Interactive
11.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element
8,810 ms
This is the largest contentful element painted within the viewport
Mobile
Minimize main-thread work
4.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift
0.06
Cumulative Layout Shift measures the movement of visible elements within the viewport
Serve images in next-gen formats
Potential savings of 75 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce initial server response time
Root document took 680 ms
Keep the server response time for the main document short because all other requests depend on it
Minify CSS
Potential savings of 72 KiB
Minifying CSS files can reduce network payload sizes
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page
Does not use HTTPS
54 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Reduce unused CSS
Potential savings of 639 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Time to Interactive
21.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy
47 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size
461 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Properly size images
Potential savings of 49 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Network Round Trip Times
90 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Avoid long main-thread tasks
14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Meaningful Paint
8.2 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce unused JavaScript
Potential savings of 522 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Defer offscreen images
Potential savings of 112 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies
210 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Avoid chaining critical requests
23 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Speed Index
18.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce the impact of third-party code
Third-party code blocked the main thread for 900 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Largest Contentful Paint element
15,120 ms
This is the largest contentful element painted within the viewport
Avoids enormous network payloads
Total size was 2,065 KiB
Large network payloads cost users real money and are highly correlated with long load times
Eliminate render-blocking resources
Potential savings of 8,540 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser
Document uses legible font sizes
99.98% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Avoid non-composited animations
7 animated elements found
Animations which are not composited can be janky and increase CLS
Enable text compression
Potential savings of 480 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Largest Contentful Paint
15.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Max Potential First Input Delay
180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time
430 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify JavaScript
Potential savings of 47 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce JavaScript execution time
2.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
8.1 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Tap targets are not sized appropriately
64% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements
Speed And Optimization Tips
Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| http://concejodeliberante.sanmartindelosandes.gov.ar/ | Internal Link | 200 |
| Inicio | Internal Link | 200 |
| NOVEDADES | Internal Link | 200 |
| ORGANIZACIÓN | Internal Link | 200 |
| EL CONCEJO DELIBERANTE | Internal Link | 200 |
| AUTORIDADES | Internal Link | 200 |
| CONCEJALES | Internal Link | 200 |
| BLOQUES POLÍTICOS | Internal Link | 200 |
| CRONOGRAMA DE SESIONES | Internal Link | 200 |
| COMISIONES | Internal Link | 200 |
| COMISIONES ESPECIALES | Internal Link | 200 |
| CONCEJALES MANDATO CUMPLIDO | Internal Link | 200 |
| NORMATIVA | Internal Link | 200 |
| DIGESTO | Internal Link | 200 |
| http://concejodeliberante.sanmartindelosandes.gov.ar/2023/09/15/sesion-ordinaria-no-20-2023/ | Internal Link | 200 |
| Sep 15, 2023 | Internal Link | 200 |
| Concejo Deliberante | Internal Link | 200 |
| http://concejodeliberante.sanmartindelosandes.gov.ar/2023/09/11/decimo-novena-sesion-ordinaria-del-2023/ | Internal Link | 200 |
| http://concejodeliberante.sanmartindelosandes.gov.ar/2023/08/25/sesion-ordinaria-no-18/ | Internal Link | 200 |
| Ago 25, 2023 | Internal Link | 200 |
Alexa Rank
99,999,999
Global Rank99,999,999
-
Traffic
Search
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| concejodeliberante.sanmartindelosandes.gov.co | Available |
| concejodeliberante.sanmartindelosandes.gov.us | Available |
| concejodeliberante.sanmartindelosandes.gov.com | Available |
| concejodeliberante.sanmartindelosandes.gov.org | Already Registered |
| concejodeliberante.sanmartindelosandes.gov.net | Already Registered |
| cncejodeliberante.sanmartindelosandes.gov.ar | Available |
| doncejodeliberante.sanmartindelosandes.gov.ar | Available |
| roncejodeliberante.sanmartindelosandes.gov.ar | Available |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Thu, 21 Sep 2023 16:12:10 GMT
Server: Apache
X-Powered-By: PHP/5.4.45
Set-Cookie: PHPSESSID=60da01a9ba73109d7c1f25d16206d9ed; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
X-UA-Compatible: IE=edge
Link: ; rel="https://api.w.org/"
Connection: close
Content-Type: text/html; charset=UTF-8