Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

fugly-bali.org

Fugly Bali - Travel / Hotels WARNING

Page Load Speed

829 ms in total

First Response

203 ms

Resources Loaded

524 ms

Page Rendered

102 ms

fugly-bali.org screenshot

About Website

Visit fugly-bali.org now to see the best up-to-date Fugly Bali content and also check out these interesting facts you probably never knew about fugly-bali.org

FUGLY BALI - Travel, health, hotels, balinese police corruption, hotel reservation agents, crime, safety and terrorism warnings for the Indonesian holiday / vacation island of Bali.

Visit fugly-bali.org

Key Findings

We analyzed Fugly-bali.org page load time and found that the first response time was 203 ms and then it took 626 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

fugly-bali.org performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value1.0 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.0 s

100/100

10%

Network Requests Diagram

fugly-bali.org

203 ms

style.css

73 ms

spacer.gif

71 ms

index_03.jpg

71 ms

index_04.jpg

73 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that all of those requests were addressed to Fugly-bali.org and no external sources were called. The less responsive or slowest element that took the longest time to load (275 ms) belongs to the original domain Fugly-bali.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.6 kB (33%)

Content Size

78.3 kB

After Optimization

52.7 kB

In fact, the total size of Fugly-bali.org main page is 78.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 49.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 21.7 kB

  • Original 25.2 kB
  • After minification 17.0 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 8.2 kB, which is 33% 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 21.7 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 1.0 kB

  • Original 49.6 kB
  • After minification 48.6 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. Fugly Bali images are well optimized though.

CSS Optimization

-83%

Potential reduce by 2.9 kB

  • Original 3.5 kB
  • After minification 2.9 kB
  • After compression 597 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. Fugly-bali.org needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (63%)

Requests Now

27

After Optimization

10

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

Accessibility Review

fugly-bali.org accessibility score

93

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

Best Practices

fugly-bali.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

fugly-bali.org SEO score

67

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fugly-bali.org 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 Fugly-bali.org main page’s claimed encoding is iso-8859-1. 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

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