Tools & Wizards About Us
worldstreets.global screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

worldstreets.global

Reverse Address Lookup Worldwide | World Streets Global

Page Load Speed

2.1 sec in total

First Response

196 ms

Resources Loaded

1.5 sec

Page Rendered

369 ms

worldstreets.global screenshot

About Website

Visit worldstreets.global now to see the best up-to-date World Streets content and also check out these interesting facts you probably never knew about worldstreets.global

Do a quick reverse address lookup in any city in the world.Search for free the up-to-date location of an address.

Visit worldstreets.global

Key Findings

We analyzed Worldstreets.global page load time and found that the first response time was 196 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

worldstreets.global performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value2,320 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.247

50/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

worldstreets.global

196 ms

worldstreets.global

488 ms

bootstrap.min.css

106 ms

blog-post.css

28 ms

bootstrap-select.min.css

118 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Worldstreets.global, 28% (11 requests) were made to Cdnjs.cloudflare.com and 15% (6 requests) were made to A.tile.openstreetmap.org. The less responsive or slowest element that took the longest time to load (488 ms) belongs to the original domain Worldstreets.global.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.4 kB (23%)

Content Size

202.4 kB

After Optimization

155.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldstreets.global main page is 202.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 86.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 40.5 kB

  • Original 48.9 kB
  • After minification 40.6 kB
  • After compression 8.4 kB

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. This page needs HTML code to be minified as it can gain 8.3 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 40.5 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 6.6 kB

  • Original 66.5 kB
  • After minification 59.9 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. World Streets images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 78 B

  • Original 86.2 kB
  • After minification 86.2 kB
  • After compression 86.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-34%

Potential reduce by 289 B

  • Original 860 B
  • After minification 860 B
  • After compression 571 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. Worldstreets.global needs all CSS files to be minified and compressed as it can save up to 289 B or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (50%)

Requests Now

36

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldstreets.global

worldstreets.global

196 ms

worldstreets.global

worldstreets.global

488 ms

bootstrap.min.css

bootstrap.min.css

106 ms

blog-post.css

blog-post.css

28 ms

bootstrap-select.min.css

bootstrap-select.min.css

118 ms

js

js

284 ms

flag-icon.min.css

flag-icon.min.css

137 ms

adsbygoogle.js

adsbygoogle.js

284 ms

leaflet.css

leaflet.css

151 ms

leaflet.js

leaflet.js

160 ms

jquery.min.js

jquery.min.js

149 ms

bootstrap-select.min.js

bootstrap-select.min.js

97 ms

bootstrap.min.js

bootstrap.min.js

157 ms

bootstrap3-typeahead.min.js

bootstrap3-typeahead.min.js

94 ms

1.png

1.png

245 ms

1.png

1.png

244 ms

2.png

2.png

397 ms

2.png

2.png

375 ms

0.png

0.png

383 ms

0.png

0.png

384 ms

3.png

3.png

383 ms

3.png

3.png

384 ms

0.png

0.png

375 ms

2.png

2.png

374 ms

2.png

2.png

384 ms

3.png

3.png

382 ms

0.png

0.png

389 ms

1.png

1.png

383 ms

1.png

1.png

403 ms

3.png

3.png

404 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

192 ms

us.svg

us.svg

344 ms

show_ads_impl.js

show_ads_impl.js

287 ms

zrt_lookup.html

zrt_lookup.html

275 ms

es.svg

es.svg

102 ms

br.svg

br.svg

97 ms

it.svg

it.svg

207 ms

fr.svg

fr.svg

100 ms

analytics.js

analytics.js

247 ms

Accessibility Review

worldstreets.global accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

worldstreets.global best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

worldstreets.global SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worldstreets.global can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Worldstreets.global main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

worldstreets.global

Open Graph description is not detected on the main page of World Streets. 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: