Your Website Score is

Similar Ranking

53
MENSAGENS COM AMOR. FRASES E MENSAGENS DE AMOR QUE FALAM POR VOCÊ.
mensagenscomamor.com
53
POSTMATES: FOOD DELIVERY, GROCERIES, ALCOHOL - ANYTHING FROM ANYWHERE
postmates.com
53
3D CAD DESIGN SOFTWARE | SOLIDWORKS
solidworks.com
53
AKAM - HABERLER - SON DAKIKA HABERLERI
aksam.com.tr
53
RECRUITING SOFTWARE | LEVER
lever.co
53
お知らせ - ZOZOTOWN
zozo.jp
53
CDMX - PORTAL CIUDADANO
cdmx.gob.mx

Latest Sites

23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.com
86
MEGOGO.NET - ФИЛЬМЫ И ТЕЛЕКАНАЛЫ ОНЛАЙН
megogo.net
59
MANOMANO : A--- EN LIGNE BRICOLAGE, RÉNOVATION ET JARDINAGE
manomano.fr
91
TECHTUDO - A TECNOLOGIA DESCOMPLICADA.
techtudo.com.br
70
AGILE PROJECT MANAGEMENT | PIVOTAL TRACKER
pivotaltracker.com
31
MOTORPLUS - PORTAL BERITA MOTOR PERTAMA DAN TERKINI
motorplus-online.com

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

53 cdmx.gob.mx Last Updated: 8 months

Success 55% of passed verification steps
Warning 15% of total warning
Errors 30% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 94%
Best Practices Desktop Score 85%
SEO Desktop Score 67%
Progressive Web App Desktop Score 54%
Performance Mobile Score 45%
Best Practices Mobile Score 85%
SEO Mobile Score 60%
Progressive Web App Mobile Score 56%
Page Authority Authority 47%
Domain Authority Domain Authority 78%
Moz Rank 4.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 23 Characters
CDMX - PORTAL CIUDADANO
Meta Description 0 Characters
NO DATA
Effective URL 19 Characters
https://cdmx.gob.mx
Excerpt Page content
CDMX - Portal Ciudadano Portal Ciudadano Portal de gobierno Turismo Tr...
Keywords Cloud Density
ciudad16 gobierno10 para8 violencia6 méxico6 mujeres4 derechos3 contra3 portal3 haciendo3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
ciudad 16
gobierno 10
para 8
violencia 6
méxico 6
mujeres 4
derechos 3
contra 3
portal 3
haciendo 3
Google Preview Your look like this in google search result
CDMX - PORTAL CIUDADANO
https://cdmx.gob.mx
CDMX - Portal Ciudadano Portal Ciudadano Portal de gobierno Turismo Tr...
Robots.txt File No Found
Sitemap.xml File No Found
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2019-05-30 / 1 year
Create on: 2014-05-29 / 6 years
Expires on: 2020-05-29 / 3 months 22 days

Akky (Una division de NIC Mexico) ,Mexico Mexico Mexico Mexico

Gobierno del Distrito Federal Eduardo Vega Sanchez Eduardo Vega Sanchez Eduardo Vega Sanchez

Nameservers
ns1.df.gob.mx
187.141.34.1
ns2.df.gob.mx
187.141.34.251
Page Size Code & Text Ratio
Document Size: ~20.55 KB
Code Size: ~14.66 KB
Text Size: ~5.89 KB Ratio: 28.65%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Serve static assets with an efficient cache policy 36 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Network Round Trip Times 0 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
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 145 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 463 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce server response times (TTFB) Root document took 690 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 170 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 375 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 43 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 0 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 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
Properly size images Potential savings of 382 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,495 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 9 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
Avoids an excessive DOM size 282 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)
Minify JavaScript Potential savings of 13 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 44 requests • 1,495 KB
To set budgets for the quantity and size of page resources, add a budget.json file

Mobile

Mobile Screenshot
Server Backend Latencies 0 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
Properly size images Potential savings of 28 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 6.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,465 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 4.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 8 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
Avoids an excessive DOM size 282 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)
Minify JavaScript Potential savings of 13 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 5.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 43 requests • 1,465 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 35 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 220 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Network Round Trip Times 0 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
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
First Contentful Paint (3G) 10269 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately 67% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document doesn't use legible font sizes 54.53% 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
Remove unused CSS Potential savings of 143 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 463 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce server response times (TTFB) Root document took 670 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,480 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 375 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 43 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 70 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
Total Blocking Time 80 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

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, 16 Jan 2020 22:30:05 GMT
Server: Apache
X-Powered-By: PHP/7.2.8
Cache-Control: no-cache, private
Set-Cookie: october_session=eyJpdiI6Ijk1RjV3VXl4SEl2MlB0cGJMWnZ6XC9nPT0iLCJ2YWx1ZSI6InRqT1dcL0dFUXJDXC96bTkycHpmaUJweUc1Rzlqa1wvNWlncFRHZmtJcmlSUDNXbWh1aVExbmhFU2tcL2dPOHY0Und0UmRtMitLc1VhUG5sQ2hVU2hRWmU2dz09IiwibWFjIjoiODRjNGZlMWExY2M3M2Y5M2M5YTY0N2JhMTM5OGRkNDRjYzdiOWRlNDFiZTUyOTc0ZGNmNmVlNDIxYjg0MGM3MCJ9; expires=Fri, 17-Jan-2020 00:30:06 GMT; Max-Age=7200; path=/; HttpOnly
Connection: close
Content-Type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome