Access progen.hu. PROGEN vállalatirányitási, ügyviteli rendszerek

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,580 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

progen.hu

328 ms

www.progen.hu

786 ms

gtm.js

80 ms

3d09ac7a88.js

112 ms

flui-post-loader.min.css

282 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 88% of them (84 requests) were addressed to the original Progen.hu, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Bat.bing.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Progen.hu.

Content Size

2.9 MB

After Optimization

2.5 MB

In fact, the total size of Progen.hu main page is 2.9 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. 55% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 274.4 kB

Original 340.4 kB
After minification 314.1 kB
After compression 66.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 274.4 kB or 81% of the original size.

Image Optimization

-9%

Potential reduce by 219.1 kB

Original 2.6 MB
After minification 2.3 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. PROGEN images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 37 B

Original 55.2 kB
After minification 55.2 kB
After compression 55.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.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

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

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

HU
Language Claimed

HU
Encoding

UTF-8

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

progen.hu

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

Report Summary

Performance

Accessibility

Best Practices

SEO

PROGEN vállalatirányitási, ügyviteli rendszerek - CRM, ERP

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

progen.hu

www.progen.hu

gtm.js

3d09ac7a88.js

flui-post-loader.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

progen.hu

www.progen.hu

gtm.js

3d09ac7a88.js

flui-post-loader.min.css

autoptimize_single_c439346315df07a42f01f66b1d8fde01.css

autoptimize_single_3fd2afa98866679439097f4ab102fe0a.css

wpcf7-redirect-frontend.min.css

autoptimize_single_7e1007fa3b22a2dd6d76e09093990e56.css

autoptimize_single_bead30b2dc0d930e1790c7346a37e1d6.css

autoptimize_single_f121cbe481654c96ce787303a88233a9.css

autoptimize_single_07752037befa9f1b8adab1bdebed6891.css

autoptimize_single_46cf7ff81cff0f4ea8401fc75154104d.css

autoptimize_single_c6a55456af4776c733018888483aba22.js

jquery.min.js

jquery-migrate.min.js

jq-sticky-anything.min.js

jquery.bind-first-0.2.3.min.js

js.cookie-2.1.3.min.js

autoptimize_single_c87c7a313aa0c6ab6c4e1adbaf762797.js

flui-post-loader.min.js

autoptimize_single_1383e4d0ef1c4475d3a93c24c1d5e906.js

autoptimize_single_efc27e253fae1b7b891fb5a40e687768.js

autoptimize_single_917602d642f84a211838f0c1757c4dc1.js

autoptimize_single_e3317d55ad904d30ea400a2da2a56686.js

hoverIntent.min.js

flatsome.js

flatsome-wp-rocket.js

autoptimize_single_fe28432f39d383868c62b57694cca31d.js

autoptimize_single_62fe89ad32c52b2cd9db03edcc663b9a.js

api.js

wp-polyfill-inert.min.js

regenerator-runtime.min.js

wp-polyfill.min.js

autoptimize_single_ec0187677793456f98473f49d9e9b95f.js

lazyload.min.js

script.js

js

fbevents.js

recorder.js

bat.js

97045236.js

log

flatsome.js