Guanajuatopress.Com.Mx - Info receives about 68 unique visitors and 68 (1.00 per visitor) page views per day which should earn about $0.28/day from advertising revenue. Estimated site value is $112.78. According to Alexa Traffic Rank is ranked number 6,310,158 in the world and 4.0E-6% of global Internet users visit it. Site is hosted in Scottsdale, Arizona, 85260, United States and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Web Servers
Font Scripts
Font Awesome
Google Font API
Programming Languages
Yoast SEO
JavaScript Libraries
jQuery Migrate
MySQL Profile

Title: Guanajuato Press |
Last update was 148 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

68 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
6,310,158 visit alexa
Alexa Reach:
4.0E-6%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Server Location:
Arizona, AZ
United States, US

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Time to Interactive 5.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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. Learn more.
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 8610 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 6.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 5.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 4.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 5.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Third-Party Usage - 4 Third-Parties Found
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. Learn more.

SizeMain Thread Time
74 KB337 ms
74 KB197 ms
9 KB52 ms
6 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1355 ms
8 ms
1366 ms
56 ms
1479 ms
21 ms
1500 ms
6 ms
1723 ms
10 ms
1734 ms
8 ms
1748 ms
21 ms
1769 ms
6 ms
1778 ms
47 ms
1828 ms
7 ms
1837 ms
18 ms
1864 ms
6 ms
2018 ms
11 ms
2032 ms
36 ms
2073 ms
6 ms
2079 ms
9 ms
2097 ms
10 ms
2218 ms
21 ms
2244 ms
8 ms
2253 ms
19 ms
2352 ms
18 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
422 ms
451 ms
5 ms
549 ms
8 ms
JavaScript execution time - 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
1055 ms25 ms9 ms
213 ms208 ms5 ms
201 ms163 ms8 ms
151 ms124 ms27 ms
77 ms15 ms3 ms
52 ms45 ms6 ms
Minify CSS - Potential savings of 6 KB
Minifying CSS files can reduce network payload sizes. Learn more.

SizePotential Savings
33 KB6 KB
Remove unused CSS - Potential savings of 66 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. Learn more.

SizePotential Savings
33 KB31 KB
12 KB12 KB
12 KB12 KB
6 KB6 KB
5 KB5 KB
Avoids enormous network payloads - Total size was 1,287 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

376 KB
295 KB
135 KB
73 KB
59 KB
55 KB
36 KB
33 KB
32 KB
22 KB
Minimizes main-thread work - 1.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Script Evaluation
707 ms
Style & Layout
471 ms
408 ms
Parse HTML & CSS
138 ms
Script Parsing & Compilation
127 ms
93 ms
Serve images in next-gen formats - Potential savings of 611 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. Learn more.

SizePotential Savings
376 KB344 KB
295 KB243 KB
135 KB24 KB
Avoids an excessive DOM size - 262 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 42 requests • 1,287 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
421287 KB
5861 KB
17170 KB
5157 KB
870 KB
326 KB
43 KB
00 KB
24217 KB
Eliminate render-blocking resources - Potential savings of 2,010 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
5 KB1080
6 KB1080
12 KB930
1 KB780
33 KB1980
1 KB480
1 KB480
12 KB1380
7 KB1230
32 KB2130
4 KB630
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms561 ms0 KB0 KB301text/html
561 ms1331 ms8 KB33 KB200text/htmlDocument
1345 ms1364 ms5 KB29 KB200text/cssStylesheet
1345 ms1364 ms6 KB23 KB200text/cssStylesheet
1346 ms1611 ms12 KB53 KB200text/cssStylesheet
1346 ms1366 ms1 KB8 KB200text/cssStylesheet
1347 ms1700 ms33 KB246 KB200text/cssStylesheet
1347 ms1415 ms1 KB0 KB200text/cssStylesheet
1347 ms1607 ms1 KB2 KB200text/cssStylesheet
1347 ms1375 ms12 KB70 KB200text/cssStylesheet
1347 ms1393 ms7 KB23 KB200application/javascriptScript
1347 ms1379 ms32 KB95 KB200application/javascriptScript
1348 ms1368 ms4 KB10 KB200application/javascriptScript
1348 ms1372 ms3 KB10 KB200application/x-javascriptScript
1348 ms1608 ms1 KB2 KB200application/javascriptScript
1348 ms1366 ms3 KB8 KB200application/javascriptScript
1348 ms1369 ms8 KB28 KB200application/javascriptScript
1349 ms1379 ms1 KB2 KB200application/javascriptScript
1349 ms1634 ms12 KB21 KB200application/javascriptScript
1349 ms1482 ms2 KB5 KB200application/javascriptScript
1349 ms1992 ms22 KB77 KB200application/javascriptScript
1350 ms1676 ms2 KB7 KB200application/javascriptScript
1350 ms1381 ms1 KB1 KB200application/javascriptScript
1350 ms1367 ms3 KB9 KB200application/x-javascriptScript
1351 ms1369 ms3 KB3 KB200application/x-javascriptScript
1416 ms1678 ms5 KB14 KB200application/javascriptScript
1420 ms1441 ms59 KB195 KB200application/x-javascriptScript
1758 ms1782 ms5 KB14 KB200text/htmlDocument
1771 ms2193 ms36 KB36 KB200font/woffFont
1771 ms2222 ms73 KB73 KB200font/woff2Font
1773 ms1778 ms14 KB13 KB200font/woff2Font
1775 ms2324 ms18 KB18 KB200font/woff2Font
1776 ms1784 ms16 KB15 KB200font/woff2Font
1866 ms1887 ms1 KB0 KB301text/html
1866 ms1887 ms1 KB0 KB301text/htmlXHR
1887 ms1911 ms1 KB0 KB200text/plainXHR
2021 ms2043 ms13 KB38 KB200text/htmlDocument
2048 ms2276 ms55 KB55 KB200image/jpegImage
2048 ms2404 ms295 KB295 KB200image/pngImage
2049 ms2615 ms135 KB135 KB200image/jpegImage
2049 ms2477 ms376 KB376 KB200image/pngImage
2069 ms2085 ms0 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms376 KB
0 ms295 KB
0 ms135 KB
0 ms73 KB
0 ms55 KB
0 ms36 KB
0 ms33 KB
0 ms22 KB
0 ms12 KB
0 ms12 KB
0 ms5 KB
0 ms2 KB
0 ms2 KB
0 ms1 KB
0 ms1 KB
0 ms1 KB
1200000 ms3 KB
259200000 ms7 KB
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. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

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. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minimize Critical Requests Depth - 26 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. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 770 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 11 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified)***dos.jpeg (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (20 minutes)

Reduce server response time

In our test, your server responded in 0.40 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 67.3KiB (18% reduction).

Compressing could save 30.1KiB (20% reduction).
Compressing could save 13.2KiB (20% reduction).
Compressing could save 12.6KiB (18% reduction).
Compressing could save 11.4KiB (15% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 3.8KiB (12% reduction).

Minifying could save 3.4KiB (11% reduction) after compression.
Minifying could save 261B (92% reduction) after compression.
Minifying could save 163B (27% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 1.4KiB (26% reduction).

Minifying could save 671B (39% reduction) after compression.
Minifying could save 367B (44% reduction) after compression.
Minifying could save 247B (12% reduction) after compression.
Minifying could save 119B (17% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 33.27 KB
Compressed size: 7.3 KB
File reduced by: 25.97 KB (78%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Upgrade: h2c
Connection: Upgrade

HTTP/2 301 
date: Thu, 01 Jan 1970 00:00:00 GMT
server: Apache
x-powered-by: PHP/7.2.20
x-redirect-by: WordPress
vary: User-Agent
content-length: 0
content-type: text/html; charset=UTF-8

HTTP/2 200 
date: Tue, 01 Oct 2019 20:12:35 GMT
server: Apache
x-powered-by: PHP/7.2.20
link: <>; rel=""
vary: Accept-Encoding,User-Agent
content-encoding: gzip
content-length: 7474
content-type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
TXT 3600
SOA 3600
Serial Number 2019091001
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 0
A 3564
NS 3564
NS 3564

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
Domain Name:

Created On: 2019-07-07
Expiration Date: 2020-07-07
Last Updated On: 2019-08-23

Name: Registration Private
City: Scottsdale
State: Arizona
Country: United States

Administrative Contact:
Name: Registration Private
City: Scottsdale
State: Arizona
Country: United States

Technical Contact:
Name: Registration Private
City: Scottsdale
State: Arizona
Country: United States

Billing Contact:
Name: Registration Private
City: Scottsdale
State: Arizona
Country: United States

Name Servers:

DNSSEC DS Records:

% NOTICE: The expiration date displayed in this record is the date the
% registrar's sponsorship of the domain name registration in the registry is
% currently set to expire. This date does not necessarily reflect the
% expiration date of the domain name registrant's agreement with the sponsoring
% registrar. Users may consult the sponsoring registrar's Whois database to
% view the registrar's reported date of expiration for this registration.

% The requested information ("Information") is provided only for the delegation
% of domain names and the operation of the DNS administered by NIC Mexico.

% It is absolutely prohibited to use the Information for other purposes,
% including sending not requested emails for advertising or promoting products
% and services purposes (SPAM) without the authorization of the owners of the
% Information and NIC Mexico.

% The database generated from the delegation system is protected by the
% intellectual property laws and all international treaties on the matter.

% If you need more information on the records displayed here, please contact us
% by email at email .

% If you want notify the receipt of SPAM or unauthorized access, please send a
% email to email .

% NOTA: La fecha de expiracion mostrada en esta consulta es la fecha que el
% registrar tiene contratada para el nombre de dominio en el registry. Esta
% fecha no necesariamente refleja la fecha de expiracion del nombre de dominio
% que el registrante tiene contratada con el registrar. Puede consultar la base
% de datos de Whois del registrar para ver la fecha de expiracion reportada por
% el registrar para este nombre de dominio.

% La informacion que ha solicitado se provee exclusivamente para fines
% relacionados con la delegacion de nombres de dominio y la operacion del DNS
% administrado por NIC Mexico.

% Queda absolutamente prohibido su uso para otros propositos, incluyendo el
% envio de Correos Electronicos no solicitados con fines publicitarios o de
% promocion de productos y servicios (SPAM) sin mediar la autorizacion de los
% afectados y de NIC Mexico.

% La base de datos generada a partir del sistema de delegacion, esta protegida
% por las leyes de Propiedad Intelectual y todos los tratados internacionales
% sobre la materia.

% Si necesita mayor informacion sobre los registros aqui mostrados, favor de
% comunic*** a email.

% Si desea notificar sobre correo no solicitado o accesos no autorizados, favor
% de enviar su mensaje a email.
Last update was 148 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites
4 secs
17 secs
42 secs
1 min
1 min
1 min
1 min
2 mins
2 mins
2 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget