Oem.Com.Mx - Info oem.com.mx

oem.com.mx receives about 15,350 unique visitors and 44,208 (2.88 per visitor) page views per day which should earn about $121.00/day from advertising revenue. Estimated site value is $77,641.47. According to Alexa Traffic Rank oem.com.mx is ranked number 32,386 in the world and 0.00307% of global Internet users visit it. Site is hosted in Ann Arbor, MI, 48104, United States and links to network IP address 35.186.198.187.

About - oem.com.mx

ORGANIZACION EDITORIAL MEXICANA
How did oem.com.mx look in the past? Edit Site Info

How popular is oem.com.mx?

Daily Unique Visitors:
15,350
Monthly Unique Visitors:
460,500
Daily Pageviews:
44,208 (2.88 per visitor)
Alexa Rank:
32,386 visit alexa
Alexa Reach:
0.00307% (Percent of global Internet users)
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic
majestic
Quantcast

Visitors by country

Users%Pageviews%Rank
Mexico 76.7%67.6%2627
United States 11.5%18.0%105309
Spain 1.8%2.0%103986

Where do visitors go on this site?

Reach%Pageviews%PerUser
oem.com.mx
67.38%68.03%1.2
cdn.oem.com.mx
19.32%18.12%1.1
hemeroteca.oem.com.mx
14.15%13.06%1.1
OTHER
0%0.77%0

Competitive Data

SEMrush oem.com.mx
Domain:
  oem.com.mx
Rank:
  1,088,081
Organic Keywords:
  2,358
Organic Traffic:
  455
Organic Cost:
  $6.00
Adwords Keywords:
  0
Adwords Traffic:
  0
Adwords Cost:
  $0.00

Data

Domain Authority:
  70
Page Authority:
  41
MozRank:
  4

Backlinks Report

Total Sites Linking In (Alexa):
2,323
Total Backlinks:
  129,062
Follow Links:
  111,728
Nofollow Links:
  17,334
Referring Domains:
  3,133
Referring IPs:
  3,057

How socially engaged is oem.com.mx?

Facebook:
  508
Google +:
  3
Linkedin:
  16
Stumbles:
  0
Buffer:
  8
Pins:
  0

How much oem.com.mx can earn?

Daily Revenue:
$121.00
Monthly Revenue:
$3,630.00
Yearly Revenue:
$44,165.00
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 7,957$91.27
Mexico 29,885$28.99
Spain 884$0.98

How much money do oem.com.mx lose due to Adblock?

Daily Revenue Loss:
$19.22
Monthly Revenue Loss:
$576.73
Yearly Revenue Loss:
$7,016.88
Daily Pageviews Blocked:
4,290
Monthly Pageviews Blocked:
128,698
Yearly Pageviews Blocked:
1,565,830
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 1,432$16.43
Mexico 2,690$2.61
Spain 168$0.19

How much is oem.com.mx worth?

Website Value:
$77,641.47

Where is oem.com.mx hosted?

Server location
Server IP:
35.186.198.187
ASN:
AS15169 
ISP:
Google Inc. 
Server Location:
Ann Arbor
MI
48104
United States
 

Other sites hosted on 35.186.198.187

There are no other sites hosted on this IP

How fast does oem.com.mx load?

Average Load Time:
(1661 ms) 52 % of sites are slower

Page Speed (Google PageSpeed Insights)

Suggestions Summary

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://oem.com.mx/
https://oem.com.mx/
https://www.oem.com.mx/oem/

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

Your page has 2 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:

https://www.oem.com.mx/oem/js/jquery-1.11.3.min.js
https://www.oem.com.mx/oem/js/bootstrap-3.3.6.js
Optimize CSS Delivery of the following:

https://www.oem.com.mx/oem/css/bootstrap-3.3.6.css
https://www.oem.com.mx/oem/css/estilos.css
https://www.oem.com.mx/oem/css/demo.css
https://www.oem.com.mx/oem/css/reset.css
https://www.oem.com.mx/oem/css/style_common.css
https://www.oem.com.mx/oem/css/style1.css
https://fonts.googleapis.com/css?family=Open+Sans

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://www.oem…m.mx/abcradio/"></a> and 3 others are close to other tap targets.
The tap target <a href="http://www.car…nd***a.com.mx"></a> is close to 1 other tap targets.
The tap target <a href="https://www.di…retaro.com.mx/">Diario De Querétaro</a> and 41 others are close to other tap targets.

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 481 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <img src="imagenes/radio.png" class="img-responsive"> falls outside the viewport.
The element <p>24 emisoras de radio.</p> falls outside the viewport.
The element <a href="#" class="info">Leer más</a> falls outside the viewport.
The element <img src="imagenes/web.png" class="img-responsive"> falls outside the viewport.
The element <p>43 Sitios web</p> falls outside the viewport.
The element <a href="#" class="info">Leer más</a> falls outside the viewport.

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 54% of the final above-the-fold content could be rendered with the full HTML response .

Optimize images

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

Optimize the following images to reduce their size by 13.7KiB (24% reduction).

Compressing https://www.oem.com.mx/oem/imagenes/fondo.png could save 3.6KiB (36% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/fondobody.png could save 2.8KiB (54% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/oem_logo.png could save 2.2KiB (13% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/Coflemex.gif could save 949B (27% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/ETV.gif could save 889B (19% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/Informex.gif could save 841B (25% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/Cia_Transportadora_Federal.gif could save 748B (24% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/Productora_Nacional_Papel.gif could save 722B (19% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/Ecofibras_Pond***a.gif could save ***1B (19% reduction).
Compressing https://www.oem.com.mx/oem/imagenes/Estudios_Tepeyac.gif could save 512B (13% reduction).

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 3.1KiB (23% reduction).

Minifying https://www.oem.com.mx/oem/js/bootstrap-3.3.6.js could save 3.1KiB (23% reduction) after compression.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Download optimized image, JavaScript, and CSS resources for this page.

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  89
Vendor reliability:
  89
Privacy:
  89
Child safety:
  85

Site Categories (dmoz)

Noticias y medios/Periódicos

What sites are related to oem.com.mx?

Http Header

HTTP/1.0 301 Moved Permanently
Server: nginx
Date: Tue, 14 Feb 2017 17:41:23 GMT
Content-Type: text/html
Content-Length: 178
Location: https://www.oem.com.mx/
X-Backend-Server: oem-2082386225-1ego7
Via: 1.1 google
HTTP/1.0 301 Moved Permanently
Server: nginx
Date: Tue, 14 Feb 2017 17:41:23 GMT
Content-Type: text/html; ch***t=UTF-8
Location: https://www.oem.com.mx/oem/
X-Backend-Server: oem-2082386225-pj851
X-Cachef: HIT
Via: 1.1 google
Alt-Svc: clear
HTTP/1.0 200 OK
Server: nginx
Date: Tue, 14 Feb 2017 17:41:23 GMT
Content-Type: text/html
Content-Length: 10602
Last-Modified: Thu, 02 Feb 2017 23:01:06 GMT
Vary: Accept-Encoding
ETag: "5893ba32-296a"
X-Backend-Server: oem-2082386225-9jlkl
Accept-Ranges: bytes
Via: 1.1 google
Alt-Svc: clear

DNS Lookup

Type Ip Target TTL
TXT 300
TXT 300
TXT 300
TXT 300
MX mail.oem.com.mx 300
MX smtp.oem.com.mx 300
SOA 3600
Mname ns-cloud-a1.googledomains.com
Rname cloud-dns-hostmaster.google.com
Serial Number 0
Refresh 21600
Retry 3600
Expire 1209600
Minimum TTL 0
A 35.186.198.187 300
NS ns-cloud-a2.googledomains.com 3600
NS ns-cloud-a4.googledomains.com 3600
NS ns-cloud-a3.googledomains.com 3600
NS ns-cloud-a1.googledomains.com 3600

Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.mx...
Domain Name: oem.com.mx

Created On: 1995-05-31
Expiration Date: 2017-05-30
Last Updated On: 2016-05-17
Registrar: Akky (Una division de NIC Mexico)
URL: http://www.akky.mx
Whois TCP URI: whois.akky.mx
Whois Web URL: http://www.akky.mx/jsf/whois/whois.jsf

Registrant:
Name: Jose Alfredo Martinez Barcenas
City: Distrito Federal
State: Distrito Federal
Country: Mexico

Administrative Contact:
Name: Ebodio Sanchez Rodriguez
City: Mexico
State: Distrito Federal
Country: Mexico

Technical Contact:
Name: Ebodio Sanchez Rodriguez
City: Mexico
State: Distrito Federal
Country: Mexico

Billing Contact:
Name: Ebodio Sanchez Rodriguez
City: Mexico
State: Distrito Federal
Country: Mexico

Name Servers:
DNS: ns-cloud-a1.googledomains.com
DNS: ns-cloud-a2.googledomains.com
DNS: ns-cloud-a3.googledomains.com
DNS: ns-cloud-a4.googledomains.com

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 222 days ago
loader
This can take up to 60 seconds. Please wait...

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) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
oem.com.mx widget