hitza.eus website information.
hitza.eus domain name is registered by .EUS top-level domain registry. See the other sites registred in .EUS domain zone.
No name server records were found.
and probably website hitza.eus is hosted by TFN-TW Taiwan Fixed Network, Telco and Network Service Provider., TW web hosting company. Check the complete list of other most popular websites hosted by TFN-TW Taiwan Fixed Network, Telco and Network Service Provider., TW hosting company.
According to Alexa traffic rank the highest website hitza.eus position was 9814 (in the world). The lowest Alexa rank position was 958401. Now website hitza.eus ranked in Alexa database as number 453589 (in the world).
Website hitza.eus Desktop speed measurement score (69/100) is better than the results of 49.24% of other sites shows that the page desktop performance can be improved.
hitza.eus Mobile usability score (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of hitza.eus (58/100) is better than the results of 50.23% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Sep-24-2024 | 453,589 | -4,693 |
| Sep-23-2024 | 448,896 | -4,563 |
| Sep-22-2024 | 444,333 | 13,607 |
| Sep-21-2024 | 457,940 | -7,011 |
| Sep-20-2024 | 450,929 | 6,776 |
| Sep-19-2024 | 457,705 | -9,940 |
| Sep-18-2024 | 447,765 | 12,258 |
Advertisement
hitza.eus Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
hitza.eus whois
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, but is also used for a wider range of other information.
hitza.eus server information
Servers Location
| IP Address |
|---|
| Country |
|---|
hitza.eus desktop page speed rank
Last tested: 2019-01-16
Desktop Speed
Medium
69/100
hitza.eus Desktop Speed Test Quick Summary
priority - 14 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 123.5KiB (44% reduction).
Compressing and resizing http://goierri.hitza.eus/files/2014/08/jaurlatiza3.png could save 66.3KiB (79% reduction).
Compressing and resizing http://hitza.eus/files/2015/06/logoa-hitza.png could save 22.4KiB (82% reduction).
Losslessly compressing http://hitza.eus/files/2014/08/hitzatako-linkak-fondoa1.png could save 7.5KiB (42% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png could save 3.4KiB (69% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png could save 3.4KiB (66% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png could save 3.3KiB (69% reduction).
Losslessly compressing http://goierri.hitza.eus/files/2014/10/urdintxoa.png could save 2.8KiB (93% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png could save 2.7KiB (96% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images…-shadow-responsive.png could save 2.2KiB (55% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/CAF-300x189.jpg could save 973B (5% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/view-icon.png could save 927B (80% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/pattern.png could save 850B (90% reduction).
Losslessly compressing http://hitza.eus/files/2015/08/IMG_4440-338x172.jpg could save 822B (5% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=251&y=186&z=9&token=32488 could save 813B (29% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png could save 805B (74% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=252&y=186&z=9&token=101309 could save 776B (27% reduction).
Losslessly compressing http://hitza.eus/files/2015/04/santuario_de_arantzazu_7460_630x-300x182.jpg could save 692B (3% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=187&z=9&token=98962 could save 673B (5% reduction).
Losslessly compressing http://maps.googleapis.com/maps/api/js/StaticMapSe…10b1&12b1&token=115208 could save 668B (10% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=253&y=186&z=9&token=39059 could save 658B (20% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=186&z=9&token=107880 could save 573B (5% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/ondarreta-harriak-300x168.jpg could save 551B (3% reduction).
Compressing and resizing http://hitza.eus/files/2015/06/logoa-hitza.png could save 22.4KiB (82% reduction).
Losslessly compressing http://hitza.eus/files/2014/08/hitzatako-linkak-fondoa1.png could save 7.5KiB (42% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png could save 3.4KiB (69% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png could save 3.4KiB (66% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png could save 3.3KiB (69% reduction).
Losslessly compressing http://goierri.hitza.eus/files/2014/10/urdintxoa.png could save 2.8KiB (93% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png could save 2.7KiB (96% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images…-shadow-responsive.png could save 2.2KiB (55% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/CAF-300x189.jpg could save 973B (5% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/view-icon.png could save 927B (80% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/pattern.png could save 850B (90% reduction).
Losslessly compressing http://hitza.eus/files/2015/08/IMG_4440-338x172.jpg could save 822B (5% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=251&y=186&z=9&token=32488 could save 813B (29% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png could save 805B (74% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=252&y=186&z=9&token=101309 could save 776B (27% reduction).
Losslessly compressing http://hitza.eus/files/2015/04/santuario_de_arantzazu_7460_630x-300x182.jpg could save 692B (3% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=187&z=9&token=98962 could save 673B (5% reduction).
Losslessly compressing http://maps.googleapis.com/maps/api/js/StaticMapSe…10b1&12b1&token=115208 could save 668B (10% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=253&y=186&z=9&token=39059 could save 658B (20% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=186&z=9&token=107880 could save 573B (5% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/ondarreta-harriak-300x168.jpg could save 551B (3% reduction).
priority - 12 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 12 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:
http://hitza.eus/wp-includes/js/jquery/jquery.js?ver=1.11.1
http://hitza.eus/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
http://hitza.eus/wp-content/themes/Observer/js/obs…r-scripts.js?ver=4.0.1
http://hitza.eus/wp-content/themes/Observer/js/respond.min.js?ver=4.0.1
http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2?
http://hitza.eus/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
http://hitza.eus/wp-content/themes/Observer/js/obs…r-scripts.js?ver=4.0.1
http://hitza.eus/wp-content/themes/Observer/js/respond.min.js?ver=4.0.1
http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2?
Optimize CSS Delivery of the following:
http://fonts.googleapis.com/css?family=Vollkorn:700
http://hitza.eus/wp-content/themes/Observer/style.css
http://hitza.eus/wp-content/plugins/easy-author-im…or-image.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/latest-custom-…c_styles.css?ver=1.3.0
http://hitza.eus/wp-content/plugins/contact-form-7…s/styles.css?ver=4.0.3
http://hitza.eus/wp-content/plugins/recent-tweets-…ter_plugin.css?ver=1.0
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?family=Oswald%3A40…%3A400%2C300&ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…-awesome.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventon-full-c…c_styles.css?ver=4.0.1
http://hitza.eus/wp-content/themes/Observer/style.css
http://hitza.eus/wp-content/plugins/easy-author-im…or-image.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/latest-custom-…c_styles.css?ver=1.3.0
http://hitza.eus/wp-content/plugins/contact-form-7…s/styles.css?ver=4.0.3
http://hitza.eus/wp-content/plugins/recent-tweets-…ter_plugin.css?ver=1.0
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?family=Oswald%3A40…%3A400%2C300&ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…-awesome.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventon-full-c…c_styles.css?ver=4.0.1
priority - 7 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:
http://hitza.eus/wp-content/plugins/geo-mashup/images/busy_icon.gif (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/pattern.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/search-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images…-shadow-responsive.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/view-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/style.css (expiration not specified)
http://connect.facebook.net/es_ES/sdk.js (20 minutes)
http://maps.google.com/maps/api/js?sensor=false&ke…&language=eu&ver=4.0.1 (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/pattern.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/search-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images…-shadow-responsive.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/view-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/style.css (expiration not specified)
http://connect.facebook.net/es_ES/sdk.js (20 minutes)
http://maps.google.com/maps/api/js?sensor=false&ke…&language=eu&ver=4.0.1 (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 6 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 54.9KiB (79% reduction).
Compressing http://hitza.eus/ could save 48.4KiB (81% reduction).
Compressing http://hitza.eus/?geo_mashup_content=render-map&ma…ap-1&wmode=transparent could save 4.4KiB (65% reduction).
Compressing http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2? could save 1.4KiB (80% reduction).
Compressing http://hitza.eus/?geo_mashup_content=geo-query&map…ject_ids=188739,131271 could save 708B (58% reduction).
Compressing http://hitza.eus/?geo_mashup_content=render-map&ma…ap-1&wmode=transparent could save 4.4KiB (65% reduction).
Compressing http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2? could save 1.4KiB (80% reduction).
Compressing http://hitza.eus/?geo_mashup_content=geo-query&map…ject_ids=188739,131271 could save 708B (58% reduction).
priority - 3 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 23.4KiB (47% reduction).
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/mxn/mxn.core.js?ver=1.8.4 could save 8.6KiB (60% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/geo-mashup.js?ver=1.8.4 could save 3.6KiB (52% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/mxn/mxn.js?ver=1.8.4 could save 3KiB (50% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/taxonomy.js?ver=1.8.4 could save 2.9KiB (43% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…ashup-mxn.js?ver=1.8.4 could save 2.4KiB (39% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…ser_front.js?ver=4.2.3 could save 2.1KiB (36% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…lev3.core.js?ver=1.8.4 could save 898B (20% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/geo-mashup.js?ver=1.8.4 could save 3.6KiB (52% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/mxn/mxn.js?ver=1.8.4 could save 3KiB (50% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/taxonomy.js?ver=1.8.4 could save 2.9KiB (43% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…ashup-mxn.js?ver=1.8.4 could save 2.4KiB (39% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…ser_front.js?ver=4.2.3 could save 2.1KiB (36% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…lev3.core.js?ver=1.8.4 could save 898B (20% reduction) after compression.
priority - 2 Reduce server response time
In our test, your server responded in 0.45 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.
priority - 1 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 10.5KiB (18% reduction).
Minifying http://hitza.eus/ could save 10.5KiB (18% reduction).
priority - 1 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 5KiB (15% reduction).
Minifying http://hitza.eus/wp-content/themes/Observer/style.css could save 2.4KiB (15% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1 could save 1.7KiB (23% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…er_front.css?ver=4.2.3 could save 948B (10% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1 could save 1.7KiB (23% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…er_front.css?ver=4.2.3 could save 948B (10% reduction) after compression.
hitza.eus Desktop Resources
| Total Resources | 120 |
| Number of Hosts | 17 |
| Static Resources | 66 |
| JavaScript Resources | 31 |
| CSS Resources | 14 |
hitza.eus Desktop Resource Breakdown
hitza.eus mobile page speed rank
Last tested: 2019-01-16
Mobile Speed
Bad
58/100
hitza.eus Mobile Speed Test Quick Summary
priority - 48 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 12 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:
http://hitza.eus/wp-includes/js/jquery/jquery.js?ver=1.11.1
http://hitza.eus/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
http://hitza.eus/wp-content/themes/Observer/js/obs…r-scripts.js?ver=4.0.1
http://hitza.eus/wp-content/themes/Observer/js/respond.min.js?ver=4.0.1
http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2?
http://hitza.eus/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1
http://hitza.eus/wp-content/themes/Observer/js/obs…r-scripts.js?ver=4.0.1
http://hitza.eus/wp-content/themes/Observer/js/respond.min.js?ver=4.0.1
http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2?
Optimize CSS Delivery of the following:
http://fonts.googleapis.com/css?family=Vollkorn:700
http://hitza.eus/wp-content/themes/Observer/style.css
http://hitza.eus/wp-content/plugins/easy-author-im…or-image.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/latest-custom-…c_styles.css?ver=1.3.0
http://hitza.eus/wp-content/plugins/contact-form-7…s/styles.css?ver=4.0.3
http://hitza.eus/wp-content/plugins/recent-tweets-…ter_plugin.css?ver=1.0
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?family=Oswald%3A40…%3A400%2C300&ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…-awesome.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventon-full-c…c_styles.css?ver=4.0.1
http://hitza.eus/wp-content/themes/Observer/style.css
http://hitza.eus/wp-content/plugins/easy-author-im…or-image.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/latest-custom-…c_styles.css?ver=1.3.0
http://hitza.eus/wp-content/plugins/contact-form-7…s/styles.css?ver=4.0.3
http://hitza.eus/wp-content/plugins/recent-tweets-…ter_plugin.css?ver=1.0
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?subset=latin%2Clat…27text%2Fcss&ver=4.0.1
http://fonts.googleapis.com/css?family=Oswald%3A40…%3A400%2C300&ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventON/assets…-awesome.css?ver=4.0.1
http://hitza.eus/wp-content/plugins/eventon-full-c…c_styles.css?ver=4.0.1
priority - 9 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:
http://hitza.eus/wp-content/plugins/geo-mashup/images/busy_icon.gif (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/ticker-shadow.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/view-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/style.css (expiration not specified)
http://connect.facebook.net/es_ES/sdk.js (20 minutes)
http://maps.google.com/maps/api/js?sensor=false&ke…&language=eu&ver=4.0.1 (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png (expiration not specified)
http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/ticker-shadow.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/images/view-icon.png (expiration not specified)
http://hitza.eus/wp-content/themes/Observer/style.css (expiration not specified)
http://connect.facebook.net/es_ES/sdk.js (20 minutes)
http://maps.google.com/maps/api/js?sensor=false&ke…&language=eu&ver=4.0.1 (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
priority - 6 Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 54.9KiB (79% reduction).
Compressing http://hitza.eus/ could save 48.4KiB (81% reduction).
Compressing http://hitza.eus/?geo_mashup_content=render-map&ma…ap-1&wmode=transparent could save 4.4KiB (65% reduction).
Compressing http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2? could save 1.4KiB (80% reduction).
Compressing http://hitza.eus/?geo_mashup_content=geo-query&map…ject_ids=188739,131271 could save 708B (58% reduction).
Compressing http://hitza.eus/?geo_mashup_content=render-map&ma…ap-1&wmode=transparent could save 4.4KiB (65% reduction).
Compressing http://p.berria.info/RealMedia/ads/adstream_mjx.ad…,Right2,Top,Top1,Top2? could save 1.4KiB (80% reduction).
Compressing http://hitza.eus/?geo_mashup_content=geo-query&map…ject_ids=188739,131271 could save 708B (58% reduction).
priority - 6 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 45.7KiB (16% reduction).
Losslessly compressing http://hitza.eus/files/2015/06/logoa-hitza.png could save 13.8KiB (50% reduction).
Losslessly compressing http://hitza.eus/files/2014/08/hitzatako-linkak-fondoa1.png could save 7.5KiB (42% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png could save 3.4KiB (69% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png could save 3.4KiB (66% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png could save 3.3KiB (69% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png could save 2.7KiB (96% reduction).
Losslessly compressing http://maps.googleapis.com/maps/api/js/StaticMapSe…s&10b1&12b1&token=4469 could save 2.2KiB (11% reduction).
Losslessly compressing http://goierri.hitza.eus/files/2014/08/jaurlatiza3.png could save 1.5KiB (2% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/CAF-300x189.jpg could save 973B (5% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/view-icon.png could save 927B (80% reduction).
Losslessly compressing http://hitza.eus/files/2015/08/IMG_4440-338x172.jpg could save 822B (5% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=251&y=186&z=9&token=32488 could save 813B (29% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png could save 805B (74% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=252&y=186&z=9&token=101309 could save 776B (27% reduction).
Losslessly compressing http://hitza.eus/files/2015/04/santuario_de_arantzazu_7460_630x-300x182.jpg could save 692B (3% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=187&z=9&token=98962 could save 673B (5% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=253&y=186&z=9&token=39059 could save 658B (20% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=186&z=9&token=107880 could save 573B (5% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/ondarreta-harriak-300x168.jpg could save 551B (3% reduction).
Losslessly compressing http://hitza.eus/files/2014/08/hitzatako-linkak-fondoa1.png could save 7.5KiB (42% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_aqua.png could save 3.4KiB (69% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_mixed.png could save 3.4KiB (66% reduction).
Losslessly compressing http://hitza.eus/wp-content/plugins/geo-mashup/images/mm_36_plus.png could save 3.3KiB (69% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/pattern-img.png could save 2.7KiB (96% reduction).
Losslessly compressing http://maps.googleapis.com/maps/api/js/StaticMapSe…s&10b1&12b1&token=4469 could save 2.2KiB (11% reduction).
Losslessly compressing http://goierri.hitza.eus/files/2014/08/jaurlatiza3.png could save 1.5KiB (2% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/CAF-300x189.jpg could save 973B (5% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/view-icon.png could save 927B (80% reduction).
Losslessly compressing http://hitza.eus/files/2015/08/IMG_4440-338x172.jpg could save 822B (5% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=251&y=186&z=9&token=32488 could save 813B (29% reduction).
Losslessly compressing http://hitza.eus/wp-content/themes/Observer/images/comments-icon.png could save 805B (74% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=252&y=186&z=9&token=101309 could save 776B (27% reduction).
Losslessly compressing http://hitza.eus/files/2015/04/santuario_de_arantzazu_7460_630x-300x182.jpg could save 692B (3% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=187&z=9&token=98962 could save 673B (5% reduction).
Losslessly compressing http://khm1.googleapis.com/kh?v=178&hl=eu&x=253&y=186&z=9&token=39059 could save 658B (20% reduction).
Losslessly compressing http://khm0.googleapis.com/kh?v=178&hl=eu&x=254&y=186&z=9&token=107880 could save 573B (5% reduction).
Losslessly compressing http://hitza.eus/files/2015/07/ondarreta-harriak-300x168.jpg could save 551B (3% reduction).
priority - 4 Reduce server response time
In our test, your server responded in 0.47 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.
priority - 3 Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 23.4KiB (47% reduction).
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/mxn/mxn.core.js?ver=1.8.4 could save 8.6KiB (60% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/geo-mashup.js?ver=1.8.4 could save 3.6KiB (52% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/mxn/mxn.js?ver=1.8.4 could save 3KiB (50% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/taxonomy.js?ver=1.8.4 could save 2.9KiB (43% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…ashup-mxn.js?ver=1.8.4 could save 2.4KiB (39% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…ser_front.js?ver=4.2.3 could save 2.1KiB (36% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…lev3.core.js?ver=1.8.4 could save 898B (20% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/geo-mashup.js?ver=1.8.4 could save 3.6KiB (52% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/mxn/mxn.js?ver=1.8.4 could save 3KiB (50% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/taxonomy.js?ver=1.8.4 could save 2.9KiB (43% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…ashup-mxn.js?ver=1.8.4 could save 2.4KiB (39% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…ser_front.js?ver=4.2.3 could save 2.1KiB (36% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/geo-mashup/js/…lev3.core.js?ver=1.8.4 could save 898B (20% reduction) after compression.
priority - 1 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 10.5KiB (18% reduction).
Minifying http://hitza.eus/ could save 10.5KiB (18% reduction).
priority - 1 Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 5KiB (15% reduction).
Minifying http://hitza.eus/wp-content/themes/Observer/style.css could save 2.4KiB (15% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1 could save 1.7KiB (23% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…er_front.css?ver=4.2.3 could save 948B (10% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/eventON/assets…n_styles.css?ver=4.0.1 could save 1.7KiB (23% reduction) after compression.
Minifying http://hitza.eus/wp-content/plugins/gattikonposer/…er_front.css?ver=4.2.3 could save 948B (10% reduction) after compression.
hitza.eus Mobile Resources
| Total Resources | 116 |
| Number of Hosts | 17 |
| Static Resources | 62 |
| JavaScript Resources | 31 |
| CSS Resources | 14 |
hitza.eus Mobile Resource Breakdown
hitza.eus mobile page usability
Last tested: 2019-01-16
Mobile Usability
Good
96/100
hitza.eus Mobile Usability Test Quick Summary
priority - 3 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 700 CSS pixels wide, but the viewport is only 320 CSS pixels wide. The following elements fall outside the viewport:
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
The element
<iframe src="http://hitza.e…de=transparent" name="gm-map-1"> falls outside the viewport.The element
<div class="vc_span4 wpb_c…lumn_container">TOKIAN TOKIKO…akostako Hitza</div> falls outside the viewport.The element
<span class="line-titlea"> falls outside the viewport.The element
<div class="vc_span4 wpb_c…lumn_container">GIZARTEA….. The post...</div> falls outside the viewport.The element
<div class="vc_span4 wpb_c…lumn_container">INGURUMENA…Gizartea</div> falls outside the viewport.The element
<div class="vc_span4 wpb_c…lumn_container">EKONOMIA…Ekonomia</div> falls outside the viewport.The element
<span class="line-titleb"> falls outside the viewport.The element
<hr> falls outside the viewport.The element
<a href="http://oarsoal…gazki-galeria/" class="small-featured-posts-title2">Xanistebanak 2…gazki galeria]</a> falls outside the viewport.The element
<hr> falls outside the viewport.The element
<h2>Azkoitia. Zara…zarna (Zestoa)</h2> falls outside the viewport.The element
<hr> falls outside the viewport.The element
<h2>Azkoitia. Zara…zarna (Zestoa)</h2> falls outside the viewport.The element
<hr> falls outside the viewport.The element
<h2>Suziria lehert…denak festara</h2> falls outside the viewport.The element
<div class="vc_span4 wpb_c…lumn_container">POLITIKA…Nabarmenak</div> falls outside the viewport.The element
<div class="vc_span12 wpb_…lumn_container"></div> falls outside the viewport.priority - 0 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://hitza.e…/gaiak/kirola/">Kirola</a> is close to 1 other tap targets.The tap target
<img src="http://maps.gs…ransparent.png"> is close to 1 other tap targets.hitza.eus similar domains
Similar domains:
www.hitza.com
www.hitza.net
www.hitza.org
www.hitza.info
www.hitza.biz
www.hitza.us
www.hitza.mobi
www.itza.eus
www.hitza.eus
www.bitza.eus
www.hbitza.eus
www.bhitza.eus
www.gitza.eus
www.hgitza.eus
www.ghitza.eus
www.yitza.eus
www.hyitza.eus
www.yhitza.eus
www.uitza.eus
www.huitza.eus
www.uhitza.eus
www.jitza.eus
www.hjitza.eus
www.jhitza.eus
www.nitza.eus
www.hnitza.eus
www.nhitza.eus
www.htza.eus
www.hutza.eus
www.hiutza.eus
www.hjtza.eus
www.hijtza.eus
www.hktza.eus
www.hiktza.eus
www.hkitza.eus
www.hotza.eus
www.hiotza.eus
www.hoitza.eus
www.hiza.eus
www.hirza.eus
www.hitrza.eus
www.hirtza.eus
www.hifza.eus
www.hitfza.eus
www.hiftza.eus
www.higza.eus
www.hitgza.eus
www.higtza.eus
www.hiyza.eus
www.hityza.eus
www.hiytza.eus
www.hita.eus
www.hitxa.eus
www.hitzxa.eus
www.hitxza.eus
www.hitsa.eus
www.hitzsa.eus
www.hitsza.eus
www.hitaa.eus
www.hitzaa.eus
www.hitaza.eus
www.hitz.eus
www.hitzq.eus
www.hitzaq.eus
www.hitzqa.eus
www.hitzw.eus
www.hitzaw.eus
www.hitzwa.eus
www.hitzs.eus
www.hitzas.eus
www.hitzz.eus
www.hitzaz.eus
www.hitzza.eus
www.hitza.net
www.hitza.org
www.hitza.info
www.hitza.biz
www.hitza.us
www.hitza.mobi
www.itza.eus
www.hitza.eus
www.bitza.eus
www.hbitza.eus
www.bhitza.eus
www.gitza.eus
www.hgitza.eus
www.ghitza.eus
www.yitza.eus
www.hyitza.eus
www.yhitza.eus
www.uitza.eus
www.huitza.eus
www.uhitza.eus
www.jitza.eus
www.hjitza.eus
www.jhitza.eus
www.nitza.eus
www.hnitza.eus
www.nhitza.eus
www.htza.eus
www.hutza.eus
www.hiutza.eus
www.hjtza.eus
www.hijtza.eus
www.hktza.eus
www.hiktza.eus
www.hkitza.eus
www.hotza.eus
www.hiotza.eus
www.hoitza.eus
www.hiza.eus
www.hirza.eus
www.hitrza.eus
www.hirtza.eus
www.hifza.eus
www.hitfza.eus
www.hiftza.eus
www.higza.eus
www.hitgza.eus
www.higtza.eus
www.hiyza.eus
www.hityza.eus
www.hiytza.eus
www.hita.eus
www.hitxa.eus
www.hitzxa.eus
www.hitxza.eus
www.hitsa.eus
www.hitzsa.eus
www.hitsza.eus
www.hitaa.eus
www.hitzaa.eus
www.hitaza.eus
www.hitz.eus
www.hitzq.eus
www.hitzaq.eus
www.hitzqa.eus
www.hitzw.eus
www.hitzaw.eus
www.hitzwa.eus
www.hitzs.eus
www.hitzas.eus
www.hitzz.eus
www.hitzaz.eus
www.hitzza.eus
hitza.eus Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
hitza.eus TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.