Tools & Wizards About Us
hapa.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

hapa.com

Printing Solutions for Pharmaceutical Packaging | HAPA

Page Load Speed

4.4 sec in total

First Response

332 ms

Resources Loaded

3.8 sec

Page Rendered

292 ms

hapa.com screenshot

About Website

Click here to check amazing HAPA content. Otherwise, check out these important facts you probably never knew about hapa.com

Are you looking for smart printing technologies and ink solutions for pharmaceutical packaging processes? Discover Hapa: find out more on our website!

Visit hapa.com

Key Findings

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

Performance Metrics

hapa.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value8,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.239

52/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

hapa.com

332 ms

www.hapa.ch

833 ms

en

159 ms

google_tag.script.js

118 ms

css_0hHz8SUrag7aEh1DKXBaPRDOUqJ6plYpg3kkXMhm9R8.css

235 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Hapa.com, 82% (27 requests) were made to Hapa.ch and 9% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Hapa.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 306.5 kB (14%)

Content Size

2.2 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hapa.com main page is 2.2 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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 45.1 kB

  • Original 53.6 kB
  • After minification 47.7 kB
  • After compression 8.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 5.9 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 45.1 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 188.5 kB

  • Original 2.0 MB
  • After minification 1.8 MB

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. HAPA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 62 B

  • Original 21.3 kB
  • After minification 21.3 kB
  • After compression 21.2 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.

CSS Optimization

-96%

Potential reduce by 72.9 kB

  • Original 75.5 kB
  • After minification 2.7 kB
  • After compression 2.7 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. Hapa.com needs all CSS files to be minified and compressed as it can save up to 72.9 kB or 96% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (14%)

Requests Now

29

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hapa.com

hapa.com

332 ms

www.hapa.ch

www.hapa.ch

833 ms

en

en

159 ms

google_tag.script.js

google_tag.script.js

118 ms

css_0hHz8SUrag7aEh1DKXBaPRDOUqJ6plYpg3kkXMhm9R8.css

css_0hHz8SUrag7aEh1DKXBaPRDOUqJ6plYpg3kkXMhm9R8.css

235 ms

css_-9yXZi0HBF1wvH1S1PD37RxLUJYpdXxkTT5dkMtS0gg.css

css_-9yXZi0HBF1wvH1S1PD37RxLUJYpdXxkTT5dkMtS0gg.css

616 ms

js_dKY5zE09kFpjwq1sWEuSTFGB82vXrvFMp_ac-Zlf9Wg.js

js_dKY5zE09kFpjwq1sWEuSTFGB82vXrvFMp_ac-Zlf9Wg.js

825 ms

HAPA_RGB.svg

HAPA_RGB.svg

390 ms

Website%20header%20%281%29.jpg

Website%20header%20%281%29.jpg

819 ms

Header_VDP_1.png

Header_VDP_1.png

1604 ms

eng_home_printing_solutions_for_lean_packaging_filter.jpg

eng_home_printing_solutions_for_lean_packaging_filter.jpg

1331 ms

support-and-services_0.jpg

support-and-services_0.jpg

1277 ms

COMPONENT_HEADER.jpg

COMPONENT_HEADER.jpg

1900 ms

Header_RA_V2.jpg

Header_RA_V2.jpg

1287 ms

Chicago_1.jpg

Chicago_1.jpg

1286 ms

H382_printed-foil-%26-people_News-header_0.jpg

H382_printed-foil-%26-people_News-header_0.jpg

1291 ms

hapa_home_global_leader_0.jpg

hapa_home_global_leader_0.jpg

1290 ms

hapa_home_hapa%20services.jpg

hapa_home_hapa%20services.jpg

1306 ms

search-black.png

search-black.png

617 ms

shadow.png

shadow.png

617 ms

placeholder.jpg

placeholder.jpg

729 ms

news.svg

news.svg

730 ms

search-white.png

search-white.png

729 ms

gtm.js

gtm.js

230 ms

icons.woff

icons.woff

344 ms

prev.png

prev.png

644 ms

next.png

next.png

645 ms

loading.gif

loading.gif

832 ms

close.png

close.png

331 ms

analytics.js

analytics.js

258 ms

js

js

114 ms

collect

collect

63 ms

collect

collect

30 ms

Accessibility Review

hapa.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

hapa.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

hapa.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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hapa.com 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 Hapa.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

hapa.com

Open Graph data is detected on the main page of HAPA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: