Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

hartza.com

Web HARTZA, sobre la obra de Javier Sáez.

Page Load Speed

1.7 sec in total

First Response

571 ms

Resources Loaded

1.1 sec

Page Rendered

99 ms

hartza.com screenshot

About Website

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

Textos, audios, videos, fotos de Javier Sáez. Información sobre teoría queer, Paco Vidarte, feminismo, políticas LGBT, antirracismo, antigitanismo. Archivos de movimientos queer.

Visit hartza.com

Key Findings

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

Performance Metrics

hartza.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

hartza.com

571 ms

OSOSGIF.gif

584 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 11.7 kB (77%)

Content Size

15.3 kB

After Optimization

3.5 kB

In fact, the total size of Hartza.com main page is 15.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 a small number of websites need less resources to load. HTML takes 15.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 11.7 kB

  • Original 15.3 kB
  • After minification 15.1 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. 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 11.7 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

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

Accessibility Review

hartza.com accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hartza.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hartza.com SEO score

79

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hartza.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Hartza.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

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