Tools & Wizards About Us
gwifi.net screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

gwifi.net

gWiFi: Using google maps to find free WiFi

Page Load Speed

1.1 sec in total

First Response

199 ms

Resources Loaded

823 ms

Page Rendered

84 ms

gwifi.net screenshot

About Website

Click here to check amazing GWiFi content. Otherwise, check out these important facts you probably never knew about gwifi.net

Using Google Maps to find free Wireless Access points.

Visit gwifi.net

Key Findings

We analyzed Gwifi.net page load time and found that the first response time was 199 ms and then it took 907 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

gwifi.net performance score

0

Network Requests Diagram

gwifi.net

199 ms

urchin.js

5 ms

header.html

44 ms

map.php

128 ms

body.php

172 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 50% of them (18 requests) were addressed to the original Gwifi.net, 19% (7 requests) were made to Maps.google.com and 8% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (249 ms) belongs to the original domain Gwifi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 724.4 kB (64%)

Content Size

1.1 MB

After Optimization

404.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gwifi.net main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 561 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 472 B

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 561 B or 54% of the original size.

Image Optimization

-7%

Potential reduce by 359 B

  • Original 4.9 kB
  • After minification 4.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. GWiFi images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 721.8 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 399.5 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 721.8 kB or 64% of the original size.

CSS Optimization

-79%

Potential reduce by 1.7 kB

  • Original 2.1 kB
  • After minification 1.6 kB
  • After compression 452 B

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Gwifi.net needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (55%)

Requests Now

29

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GWiFi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

gwifi.net

gwifi.net

199 ms

urchin.js

urchin.js

5 ms

header.html

header.html

44 ms

map.php

map.php

128 ms

body.php

body.php

172 ms

footer.php

footer.php

191 ms

__utm.gif

__utm.gif

2 ms

stylesheet.css

stylesheet.css

108 ms

index_01.gif

index_01.gif

141 ms

index_02.gif

index_02.gif

180 ms

maps

maps

71 ms

stylesheet.css

stylesheet.css

120 ms

show_ads.js

show_ads.js

5 ms

bg.gif

bg.gif

128 ms

green.png

green.png

181 ms

grey.png

grey.png

182 ms

gold.png

gold.png

222 ms

red.png

red.png

249 ms

tinc

tinc

159 ms

zrt_lookup.html

zrt_lookup.html

33 ms

show_ads_impl.js

show_ads_impl.js

34 ms

refresh.gif

refresh.gif

184 ms

ads

ads

60 ms

osd.js

osd.js

60 ms

common.js

common.js

12 ms

map.js

map.js

11 ms

overlay.js

overlay.js

10 ms

green.png

green.png

132 ms

tinc

tinc

161 ms

grey.png

grey.png

191 ms

util.js

util.js

21 ms

onion.js

onion.js

21 ms

openhand_8_8.cur

openhand_8_8.cur

42 ms

gold.png

gold.png

187 ms

red.png

red.png

190 ms

infowindow.js

infowindow.js

2 ms

Accessibility Review

gwifi.net accessibility score

33

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

gwifi.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gwifi.net SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gwifi.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gwifi.net main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

gwifi.net

Open Graph description is not detected on the main page of GWiFi. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: