Tools & Wizards About Us
indietown.com screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    95% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

indietown.com

Layanan Hosting Indonesia dan USA, Solusi web bisnis :: indieTown.com

Page Load Speed

2.2 sec in total

First Response

857 ms

Resources Loaded

1.1 sec

Page Rendered

175 ms

indietown.com screenshot

About Website

Visit indietown.com now to see the best up-to-date IndieTown content for Indonesia and also check out these interesting facts you probably never knew about indietown.com

indieTown merupakan penyedia jasa pembuatan situs web, hosting, dan registrasi domain di Indonesia. Server Linux-CentOS di datacenter IIX dan USA

Visit indietown.com

Key Findings

We analyzed Indietown.com page load time and found that the first response time was 857 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

indietown.com performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

86/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

indietown.com

857 ms

style.css

52 ms

bt_home.gif

48 ms

bt_en.gif

66 ms

bt_rss.gif

124 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 13.5 kB (16%)

Content Size

86.8 kB

After Optimization

73.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Indietown.com main page is 86.8 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. Only 10% of websites need less resources to load. Images take 69.6 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 5.9 kB

  • Original 8.8 kB
  • After minification 8.5 kB
  • After compression 3.0 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 5.9 kB or 66% of the original size.

Image Optimization

-2%

Potential reduce by 1.1 kB

  • Original 69.6 kB
  • After minification 68.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. IndieTown images are well optimized though.

CSS Optimization

-78%

Potential reduce by 6.5 kB

  • Original 8.3 kB
  • After minification 6.5 kB
  • After compression 1.8 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. Indietown.com needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

20

After Optimization

9

  • Images
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IndieTown. 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.

Network Requests Diagram

indietown.com

indietown.com

857 ms

style.css

style.css

52 ms

bt_home.gif

bt_home.gif

48 ms

bt_en.gif

bt_en.gif

66 ms

bt_rss.gif

bt_rss.gif

124 ms

bg_terusan.png

bg_terusan.png

124 ms

logo_vendors.gif

logo_vendors.gif

131 ms

logo.png

logo.png

112 ms

bt_temukan.png

bt_temukan.png

95 ms

tx_news.gif

tx_news.gif

172 ms

tx_hubungi.gif

tx_hubungi.gif

138 ms

bt_kirim.png

bt_kirim.png

157 ms

bg_hovertop.png

bg_hovertop.png

166 ms

bg_corner.gif

bg_corner.gif

172 ms

bg.png

bg.png

121 ms

bg_outer.gif

bg_outer.gif

196 ms

bg_outerct.gif

bg_outerct.gif

154 ms

bg_content.jpg

bg_content.jpg

180 ms

ico.png

ico.png

170 ms

bg_logo.png

bg_logo.png

217 ms

bg_inputs.png

bg_inputs.png

228 ms

Accessibility Review

indietown.com accessibility score

43

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

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

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

Best Practices

indietown.com 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

indietown.com SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ID

  • Language Claimed

    ID

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indietown.com can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it matches the claimed language. Our system also found out that Indietown.com 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

indietown.com

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