22 sec in total
511 ms
14.2 sec
7.2 sec
Welcome to hai-in.ro homepage info - get ready to check Hai In best content for Romania right away, or after learning these important things about hai-in.ro
Anunțuri gratuite online, de la persoane fizice si firme. Adaugă anunț gratuite in imobiliare, auto, telefoane mobile, apartamente de închiriat si de vânzare, mașini second hand, haine.
Visit hai-in.roWe analyzed Hai-in.ro page load time and found that the first response time was 511 ms and then it took 21.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
hai-in.ro performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value5.2 s
23/100
25%
Value14.8 s
1/100
10%
Value1,600 ms
12/100
30%
Value0.381
27/100
15%
Value17.1 s
4/100
10%
511 ms
1735 ms
399 ms
566 ms
464 ms
Our browser made a total of 171 requests to load all elements on the main page. We found that 78% of them (133 requests) were addressed to the original Hai-in.ro, 3% (5 requests) were made to Pagead2.googlesyndication.com and 2% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Googletagservices.com.
Page size can be reduced by 309.5 kB (23%)
1.3 MB
1.0 MB
In fact, the total size of Hai-in.ro main page is 1.3 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 a small number of websites need less resources to load. Javascripts take 386.7 kB which makes up the majority of the site volume.
Potential reduce by 233.2 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 233.2 kB or 84% of the original size.
Potential reduce by 33.6 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. Hai In images are well optimized though.
Potential reduce by 20.9 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.
Potential reduce by 21.9 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. Hai-in.ro has all CSS files already compressed.
Number of requests can be reduced by 134 (85%)
158
24
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hai In. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 89 to 1 for JavaScripts and from 47 to 1 for CSS and as a result speed up the page load time.
hai-in.ro
511 ms
hai-in.ro
1735 ms
wp-emoji-release.min.js
399 ms
bootstrap.min.css
566 ms
slick.css
464 ms
slick-theme.css
472 ms
styles.css
509 ms
pacz-styles.css
681 ms
pacz-blog.css
509 ms
common-shortcode.css
586 ms
fonticon-custom.min.css
740 ms
common.css
623 ms
style.min.css
631 ms
wpforms-full.min.css
733 ms
font-awesome.min.css
109 ms
frontend.css
868 ms
buttons.min.css
791 ms
dashicons.min.css
812 ms
mediaelementplayer-legacy.min.css
829 ms
wp-mediaelement.min.css
826 ms
media-views.min.css
829 ms
imgareaselect.css
902 ms
style.css
903 ms
common-style.css
921 ms
directorypress-frontend-messages-public.css
921 ms
style.css
929 ms
directorypress-frontend-public.css
952 ms
directorypress-listings.css
973 ms
select2.css
970 ms
jquery-ui.min.css
236 ms
all.min.css
975 ms
slick.css
1043 ms
slick-theme.css
1045 ms
directorypress-search.css
1066 ms
style.css
1071 ms
style.css
1069 ms
style.css
1149 ms
front.min.css
1164 ms
font-awesome.min.css
1165 ms
amp-ad-0.1.js
238 ms
js
261 ms
css
242 ms
adsbygoogle.js
281 ms
style.css
1082 ms
listing-style-14.css
860 ms
js_composer.min.css
917 ms
custom.css
842 ms
classiadspro-dynamic.css
794 ms
Defaults.css
838 ms
typo.css
783 ms
animate.min.css
1042 ms
directorypress-dynamic.css
992 ms
jquery.min.js
1023 ms
jquery-migrate.min.js
930 ms
frontend.js
875 ms
utils.min.js
871 ms
moxie.min.js
1005 ms
plupload.min.js
827 ms
directorypress-frontend-messages-public.js
973 ms
scripts.js
1781 ms
directorypress-frontend-public.js
1429 ms
directorypress-frontend-profile.js
1414 ms
directorypress-frontend-listing.js
1352 ms
chart.min.js
1392 ms
core.min.js
1337 ms
tabs.min.js
1450 ms
bootstrap.min.js
1461 ms
imagesloaded.min.js
1472 ms
masonry.min.js
1447 ms
select2.min.js
1570 ms
slick.min.js
1502 ms
plugins.min.js
1815 ms
theme-scripts.js
1815 ms
triger.min.js
1467 ms
custom.js
1727 ms
comment-reply.min.js
1712 ms
underscore.min.js
1697 ms
shortcode.min.js
1697 ms
backbone.min.js
1699 ms
wp-util.min.js
1648 ms
wp-backbone.min.js
1771 ms
media-models.min.js
1771 ms
wp-plupload.min.js
1767 ms
mouse.min.js
1722 ms
sortable.min.js
1720 ms
mediaelement-and-player.min.js
1481 ms
mediaelement-migrate.min.js
1498 ms
wp-mediaelement.min.js
1492 ms
api-request.min.js
1486 ms
regenerator-runtime.min.js
1483 ms
wp-polyfill.min.js
1477 ms
dom-ready.min.js
1340 ms
hooks.min.js
1573 ms
i18n.min.js
1542 ms
a11y.min.js
1530 ms
clipboard.min.js
1114 ms
media-views.min.js
1115 ms
media-editor.min.js
1178 ms
media-audiovideo.min.js
1176 ms
resizable.min.js
1174 ms
draggable.min.js
1111 ms
controlgroup.min.js
1084 ms
checkboxradio.min.js
1268 ms
button.min.js
1266 ms
dialog.min.js
1369 ms
menu.min.js
1154 ms
selectmenu.min.js
1147 ms
logo-hr.png
2051 ms
6f6ced349487f14709bea3cf27202eab
294 ms
5682879d66d6348df340da6d9a3139c5
294 ms
autocomplete.min.js
823 ms
select2.min.js
995 ms
select2-triger.js
991 ms
masonry.pkgd.min.js
990 ms
lightbox.min.js
989 ms
lity.min.js
988 ms
slick-triger.min.js
1856 ms
jquery.cookie.js
1855 ms
analytics.js
353 ms
directorypress-terms.js
1688 ms
contact-form.js
819 ms
directorypress-public.js
1021 ms
front.min.js
1020 ms
slider.min.js
1020 ms
jquery.ui.touch-punch.js
1027 ms
KFOmCnqEu92Fr1Mu4mxM.woff
402 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
408 ms
js_composer_front.min.js
1628 ms
vc-waypoints.min.js
1624 ms
glyphicons-halflings-regular.woff
1620 ms
fa-solid-900.woff
1666 ms
fa-regular-400.woff
1627 ms
classiadspro-light-logo.png
1626 ms
zrt_lookup.html
367 ms
FB_IMG_1596170122005-pa1ol0miljmkbnjkund4ol4f0xv3dvd9wuy6xo8dt8.jpg
1419 ms
FB_IMG_1596170131753-1-pa1okyqu7vjzofmb5mjvjllhu64cyh5t8ln7z4b65o.jpg
1392 ms
FB_IMG_1596170125497-pa1nvsmf7l3ksc6i4qviry956q6iu98kg0r5cdmorw.jpg
1397 ms
FB_IMG_1596170248194-pa1nwahctfs0wxgk8glflbqwh1qhwi7guh5dgmw7ho.jpg
1391 ms
FB_IMG_1596170128991-1-pa1nwg4dyfzqul8dbj170abo1cyp6otuv92acanugc.jpg
1655 ms
collect
397 ms
FB_IMG_1576208938302-pa1ola0whvzfjr5xbrfedir0yskriuela5h1qfug30.jpg
1988 ms
no-thumbnail.jpg
1303 ms
show_ads_impl.js
363 ms
collect
876 ms
selectbox-arrow.png
1130 ms
ga-audiences
720 ms
pacz-fic2.woff
1163 ms
fontawesome-webfont.woff
1160 ms
fontawesome-webfont.woff
1160 ms
fontawesome-webfont.woff
419 ms
cookie.js
628 ms
integrator.js
1104 ms
ads
878 ms
85254efcadaacab5fed344cbf203b7e7.js
1033 ms
load_preloaded_resource.js
1706 ms
c471d9b7113df21a6cf58632ab968748.js
1486 ms
abg_lite.js
1800 ms
window_focus.js
1813 ms
qs_click_protection.js
1813 ms
rx_lidar.js
2822 ms
042791247ab671b2831aa311d6583330.js
1484 ms
icon.png
651 ms
integrator.js
82 ms
ui-bg_flat_75_ffffff_40x100.png
17 ms
s
50 ms
css
61 ms
sodar
699 ms
activeview
76 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpy8.woff
63 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpy8.woff
61 ms
f36U5LLOSFCl_RQcRb4gz5dtt8ZR3FgOTI7LNXASQxk.js
32 ms
hai-in.ro accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hai-in.ro best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hai-in.ro SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hai-in.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Hai-in.ro 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.
hai-in.ro
Open Graph data is detected on the main page of Hai In. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: