Tools & Wizards About Us
indyhamfest.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

indyhamfest.com

Indianapolis Communications & Technology Expo (formerly "The Indianapolis Hamfest")

Page Load Speed

875 ms in total

First Response

140 ms

Resources Loaded

655 ms

Page Rendered

80 ms

indyhamfest.com screenshot

About Website

Welcome to indyhamfest.com homepage info - get ready to check Indy Hamfest best content right away, or after learning these important things about indyhamfest.com

Indianapolis Hamfest and Communications Expo

Visit indyhamfest.com

Key Findings

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

Performance Metrics

indyhamfest.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value0.8 s

100/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

indyhamfest.com

140 ms

ga.js

6 ms

ihlogo.jpg

57 ms

IHA-51%20NO%20BKGND.png

405 ms

ARRL_Foundation_Logo.jpg

158 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 69% of them (9 requests) were addressed to the original Indyhamfest.com, 31% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (405 ms) belongs to the original domain Indyhamfest.com.

Page Optimization Overview & Recommendations

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

Content Size

335.2 kB

After Optimization

258.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Indyhamfest.com main page is 335.2 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 313.0 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 3.3 kB

  • Original 5.0 kB
  • After minification 4.9 kB
  • After compression 1.7 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 3.3 kB or 66% of the original size.

Image Optimization

-24%

Potential reduce by 73.8 kB

  • Original 313.0 kB
  • After minification 239.2 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. Obviously, Indy Hamfest needs image optimization as it can save up to 73.8 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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.

Requests Breakdown

We found no issues to fix!

Requests Now

12

After Optimization

12

  • Images
  • JavaScript

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indy Hamfest. According to our analytics all requests are already optimized.

Network Requests Diagram

indyhamfest.com

indyhamfest.com

140 ms

ga.js

ga.js

6 ms

ihlogo.jpg

ihlogo.jpg

57 ms

IHA-51%20NO%20BKGND.png

IHA-51%20NO%20BKGND.png

405 ms

ARRL_Foundation_Logo.jpg

ARRL_Foundation_Logo.jpg

158 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

6 ms

__utm.gif

__utm.gif

6 ms

button49.gif

button49.gif

67 ms

button5B.gif

button5B.gif

61 ms

button5D.gif

button5D.gif

72 ms

button6.gif

button6.gif

108 ms

button7.gif

button7.gif

108 ms

Accessibility Review

indyhamfest.com accessibility score

68

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

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indyhamfest.com 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 Indyhamfest.com main page’s claimed encoding is windows-1252. 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

indyhamfest.com

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