Tools & Wizards About Us
halleyweb.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

halleyweb.com

Page Load Speed

3.6 sec in total

First Response

583 ms

Resources Loaded

2.9 sec

Page Rendered

117 ms

halleyweb.com screenshot

About Website

Welcome to halleyweb.com homepage info - get ready to check Halleyweb best content for Italy right away, or after learning these important things about halleyweb.com

Visit halleyweb.com

Key Findings

We analyzed Halleyweb.com page load time and found that the first response time was 583 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

halleyweb.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.8 s

100/100

25%

SI (Speed Index)

Value1.1 s

100/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

index.php

583 ms

scripts.js

982 ms

bootstrap.min.js

321 ms

bootstrap.halley.js

222 ms

bootstrap.min.css

445 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (76%)

Content Size

1.7 MB

After Optimization

407.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Halleyweb.com main page is 1.7 MB. 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. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.7 kB

  • Original 12.1 kB
  • After minification 10.7 kB
  • After compression 3.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 1.4 kB, which is 11% 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 8.7 kB or 72% of the original size.

Image Optimization

-19%

Potential reduce by 1.3 kB

  • Original 7.3 kB
  • After minification 5.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. Obviously, Halleyweb needs image optimization as it can save up to 1.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-75%

Potential reduce by 1.0 MB

  • Original 1.4 MB
  • After minification 1.2 MB
  • After compression 351.4 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 1.0 MB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 253.6 kB

  • Original 299.9 kB
  • After minification 254.0 kB
  • After compression 46.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. Halleyweb.com needs all CSS files to be minified and compressed as it can save up to 253.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (44%)

Requests Now

16

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.php

index.php

583 ms

scripts.js

scripts.js

982 ms

bootstrap.min.js

bootstrap.min.js

321 ms

bootstrap.halley.js

bootstrap.halley.js

222 ms

bootstrap.min.css

bootstrap.min.css

445 ms

bootstrap-override.css

bootstrap-override.css

227 ms

style.css

style.css

571 ms

ckeditor.js

ckeditor.js

1090 ms

accessibilita.php

accessibilita.php

448 ms

sfondomenu.png

sfondomenu.png

109 ms

assopa-badge.png

assopa-badge.png

211 ms

yellow_wai-aa.gif

yellow_wai-aa.gif

221 ms

valid_html5.png

valid_html5.png

218 ms

valid_css3.png

valid_css3.png

223 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

623 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

550 ms

print.css

print.css

221 ms

Accessibility Review

halleyweb.com accessibility score

68

Accessibility Issues

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

Document doesn't have a <title> element

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

halleyweb.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

halleyweb.com SEO score

50

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    IT

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Halleyweb.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Italian. Our system also found out that Halleyweb.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

halleyweb.com

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