Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 0

    Best Practices

  • 62

    SEO

    Google-friendlier than
    22% of websites

alize.us

loc.alize.us - Explore your world through everyone's eyes

Page Load Speed

2.7 sec in total

First Response

518 ms

Resources Loaded

2 sec

Page Rendered

197 ms

alize.us screenshot

About Website

Visit alize.us now to see the best up-to-date Alize content and also check out these interesting facts you probably never knew about alize.us

loc.alize.us displays a massiv amount of photos on a highly interactive world map. Explore photos from everyone's places, selected topics or people you know.

Visit alize.us

Key Findings

We analyzed Alize.us page load time and found that the first response time was 518 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

alize.us performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

loc.alize.us

518 ms

localize_packaged.css

320 ms

buddyicon.jpg

51 ms

maps

56 ms

localize_packaged.js

774 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Alize.us, 20% (10 requests) were made to Maps.gstatic.com and 16% (8 requests) were made to Khms1.googleapis.com. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source Loc.alize.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 461.2 kB (52%)

Content Size

887.4 kB

After Optimization

426.1 kB

In fact, the total size of Alize.us main page is 887.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. 45% of websites need less resources to load. Javascripts take 601.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 49.8 kB

  • Original 57.3 kB
  • After minification 53.3 kB
  • After compression 7.5 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. 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 49.8 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 12.3 kB

  • Original 220.0 kB
  • After minification 207.8 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. Alize images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 393.2 kB

  • Original 601.7 kB
  • After minification 601.7 kB
  • After compression 208.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 393.2 kB or 65% of the original size.

CSS Optimization

-72%

Potential reduce by 6.0 kB

  • Original 8.3 kB
  • After minification 8.2 kB
  • After compression 2.3 kB

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. Alize.us needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (28%)

Requests Now

46

After Optimization

33

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

Accessibility Review

alize.us accessibility score

72

Accessibility Issues

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

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

Image elements do not have [alt] attributes

SEO Factors

alize.us SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alize.us 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 Alize.us 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

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