Tools & Wizards About Us
capitris.hu screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

capitris.hu

Ügyfélszolgálati és call center szoftver | Adertis

Page Load Speed

3.9 sec in total

First Response

321 ms

Resources Loaded

2.9 sec

Page Rendered

653 ms

capitris.hu screenshot

About Website

Click here to check amazing Capitris content for Hungary. Otherwise, check out these important facts you probably never knew about capitris.hu

Felhőalapú telefonos ügyfélkezelő rendszer és call center szoftver egyben, folyamatos programfrissítéssel és helpdesk támogatással

Visit capitris.hu

Key Findings

We analyzed Capitris.hu page load time and found that the first response time was 321 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

capitris.hu performance score

0

Network Requests Diagram

capitris.hu

321 ms

www.adertis.hu

644 ms

script.js

31 ms

wpsol_40b737e1b11eac5fafaffaa2abd946ac.css

318 ms

wpsol_854e0ad51190dde56e7fa884629722e6.css

317 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Capitris.hu, 93% (57 requests) were made to Adertis.hu and 2% (1 request) were made to Cdn-cookieyes.com. The less responsive or slowest element that took the longest time to load (871 ms) relates to the external source Adertis.hu.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.1 kB (17%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 64.2 kB

  • Original 78.3 kB
  • After minification 78.2 kB
  • After compression 14.1 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 64.2 kB or 82% of the original size.

Image Optimization

-13%

Potential reduce by 174.8 kB

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

JavaScript Optimization

-11%

Potential reduce by 12.9 kB

  • Original 114.4 kB
  • After minification 114.4 kB
  • After compression 101.5 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 12.9 kB or 11% of the original size.

CSS Optimization

-24%

Potential reduce by 9.3 kB

  • Original 39.4 kB
  • After minification 39.4 kB
  • After compression 30.1 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. Capitris.hu needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 24% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

51

  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Capitris. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

capitris.hu

capitris.hu

321 ms

www.adertis.hu

www.adertis.hu

644 ms

script.js

script.js

31 ms

wpsol_40b737e1b11eac5fafaffaa2abd946ac.css

wpsol_40b737e1b11eac5fafaffaa2abd946ac.css

318 ms

wpsol_854e0ad51190dde56e7fa884629722e6.css

wpsol_854e0ad51190dde56e7fa884629722e6.css

317 ms

wpsol_eadc7c216c9dc683f8102e93e88258ca.css

wpsol_eadc7c216c9dc683f8102e93e88258ca.css

325 ms

wpsol_a39646c68d60652de2f014791a1f32cc.css

wpsol_a39646c68d60652de2f014791a1f32cc.css

324 ms

js

js

60 ms

log

log

400 ms

jquery.min.js

jquery.min.js

329 ms

wpsol_b37d7edf99565d3858eaa1ad80df3cff.js

wpsol_b37d7edf99565d3858eaa1ad80df3cff.js

317 ms

wpsol_a5cd0445a1934ed16502084e6d771595.js

wpsol_a5cd0445a1934ed16502084e6d771595.js

322 ms

adertis-logo-414x128.png

adertis-logo-414x128.png

109 ms

adertis-header-08-scaled.jpg

adertis-header-08-scaled.jpg

213 ms

adertis-nyitooldal-fokep-2.png

adertis-nyitooldal-fokep-2.png

768 ms

adertis-nyitooldal-fokep.png

adertis-nyitooldal-fokep.png

534 ms

adertis-nyitooldal-ikon-01b.jpg

adertis-nyitooldal-ikon-01b.jpg

184 ms

adertis-nyitooldal-ikon-02b.jpg

adertis-nyitooldal-ikon-02b.jpg

193 ms

adertis-nyitooldal-ikon-03.jpg

adertis-nyitooldal-ikon-03.jpg

322 ms

adertis-bckgr-01b-scaled.jpg

adertis-bckgr-01b-scaled.jpg

290 ms

adertis-konzultacio-01.png

adertis-konzultacio-01.png

408 ms

nielsen.png

nielsen.png

318 ms

bellresearch.png

bellresearch.png

396 ms

mentavill.png

mentavill.png

424 ms

eudiakok.png

eudiakok.png

430 ms

lira.png

lira.png

501 ms

szegimedical.png

szegimedical.png

516 ms

header-tlogo-100_50.png

header-tlogo-100_50.png

529 ms

fabian.jpg

fabian.jpg

537 ms

kocsiguru.jpg

kocsiguru.jpg

608 ms

radium.png

radium.png

623 ms

miele.png

miele.png

635 ms

e2hun.png

e2hun.png

637 ms

EU-Solar-1.png

EU-Solar-1.png

645 ms

otthondepo.png

otthondepo.png

713 ms

hrmcenter.jpeg

hrmcenter.jpeg

731 ms

emineo.png

emineo.png

740 ms

erzsebetfurdo.png

erzsebetfurdo.png

741 ms

iqbmedical.png

iqbmedical.png

752 ms

saldo.jpg

saldo.jpg

818 ms

heavytools.png

heavytools.png

839 ms

erste.png

erste.png

847 ms

mindentment.png

mindentment.png

846 ms

pelsokom.png

pelsokom.png

860 ms

doktor24.png

doktor24.png

826 ms

bestbyte.png

bestbyte.png

855 ms

foxpost.png

foxpost.png

871 ms

pharmacloud.png

pharmacloud.png

851 ms

oktogonmedical-1.png

oktogonmedical-1.png

846 ms

wotan.png

wotan.png

786 ms

kutyubazar.png

kutyubazar.png

790 ms

nak.png

nak.png

822 ms

tkk.png

tkk.png

766 ms

czeizel.png

czeizel.png

740 ms

ujfurdo.png

ujfurdo.png

737 ms

bmm.jpg

bmm.jpg

682 ms

aesthetica.png

aesthetica.png

682 ms

adertis-nyitooldal-kapcsolat-01.jpg

adertis-nyitooldal-kapcsolat-01.jpg

821 ms

adertis-logo-414x128-white-300x93.png

adertis-logo-414x128-white-300x93.png

734 ms

ISO9001Reg-2cm-Col.jpg

ISO9001Reg-2cm-Col.jpg

660 ms

ISO27001Reg-2cm-Col.jpg

ISO27001Reg-2cm-Col.jpg

649 ms

SEO Factors

capitris.hu SEO score

0

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

capitris.hu

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