3.3 sec in total
208 ms
2.6 sec
481 ms
Welcome to kasih.com homepage info - get ready to check Kasih best content right away, or after learning these important things about kasih.com
The manufacture of halva and tahini is strongly associated with the KASIH family name. It was the first factory in Amman in 1998.
Visit kasih.comWe analyzed Kasih.com page load time and found that the first response time was 208 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
kasih.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value26.3 s
0/100
25%
Value9.6 s
11/100
10%
Value1,830 ms
9/100
30%
Value0.045
99/100
15%
Value18.2 s
3/100
10%
208 ms
569 ms
201 ms
301 ms
400 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 76% of them (78 requests) were addressed to the original Kasih.com, 9% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (828 ms) belongs to the original domain Kasih.com.
Page size can be reduced by 1.2 MB (32%)
3.7 MB
2.5 MB
In fact, the total size of Kasih.com main page is 3.7 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. 60% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 80.9 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 80.9 kB or 87% of the original size.
Potential reduce by 1.1 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, Kasih needs image optimization as it can save up to 1.1 MB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 16.7 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 8.8 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. Kasih.com needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 17% of the original size.
Number of requests can be reduced by 42 (48%)
88
46
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kasih. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
kasih.com
208 ms
www.kasih.com
569 ms
bootstrap.min.css
201 ms
KASIH.css
301 ms
style.css
400 ms
all.min.css
62 ms
animate.min.css
412 ms
animate.css
409 ms
styles.css
413 ms
jquery-latest.min.js
508 ms
script.js
462 ms
jquery.js
499 ms
amazingcarousel.js
608 ms
initcarousel-1.css
528 ms
initcarousel-1.js
528 ms
tipsy.css
577 ms
litebox.css
598 ms
slick.min.css
606 ms
style.css
611 ms
style.css
611 ms
set1.css
693 ms
responsive.css
698 ms
js
73 ms
js
118 ms
js
128 ms
js
135 ms
bootstrap.min.js
695 ms
jquery.fittext.js
695 ms
wow.min.js
695 ms
creative.js
696 ms
main.js
781 ms
slick.min.js
779 ms
lazysizes.min.js
779 ms
script.js
781 ms
smoothscroll.min.js
782 ms
images-loaded.min.js
780 ms
tipsy.min.js
801 ms
backbone.js
809 ms
litebox.min.js
824 ms
css
41 ms
scevent.min.js
40 ms
css
17 ms
embed
287 ms
logo-en.png
495 ms
header-bg.png
600 ms
ece03820-d1eb-4e7f-9feb-ce5e3e0fadbe.png
399 ms
9a123f69-b141-4724-8268-0f73ee44ef73.webp
486 ms
26f32982-a500-4fff-8429-5867074bce56.webp
319 ms
e4d752fe-0721-4c0e-9379-cc7f1af9de7e.webp
338 ms
ee4faefc-c6fd-4061-bce4-5ede20a599b5.webp
397 ms
9d34164d-1a75-4c55-9bf6-11d56cc40ace.webp
454 ms
3d355d14-abd7-444e-ad69-3e4952f8029a.webp
695 ms
5cfb7b70-1d3d-4ca7-a354-bbcae0f8bb07.webp
500 ms
d8bef046-da31-4b04-a865-5b1fb48bfe80.webp
683 ms
178a5241-43e2-4ce4-bc7c-3d00db21d123.webp
585 ms
d9bdd99e-8bdf-473e-92ff-e1c3855e3ea4.webp
593 ms
1a1da499-421d-4086-abdb-bc76d1bccb55.webp
601 ms
77afc885-f408-4573-81ac-2e89364e2190.webp
685 ms
cf61cb72-6762-407d-9e76-1c27594f1e19.webp
693 ms
0c984242-7312-4d77-a85a-117a2869c86a.webp
698 ms
e1905d83-715d-4883-84c4-3a85b2169454.webp
701 ms
c603dc1e-4186-4268-8845-2b09af5cf0d6.webp
798 ms
0f3dee43-5381-462c-b947-473f5a432a8e.webp
784 ms
5619236c-27ac-4961-a0a3-bff6141d0afe.webp
792 ms
53cfd1bd-aaf2-46e4-8a7f-58903b2666be.webp
793 ms
14ab9988-6bf7-4c84-a27b-6eac6a95ba45.webp
720 ms
4cb8b2c2-f2f1-4867-8bd8-e23fced798f5.webp
725 ms
c2537444-08e3-4b5c-a306-166ae937fb67.webp
807 ms
196e8cd2-9b4e-410c-a052-55d149abc7cb.webp
814 ms
77f72a73-6fc5-4020-bfe1-bde24dc506e0.webp
730 ms
2c46d38b-1a64-47bb-82fe-8b45eb85e0b7.webp
734 ms
2819c73d-2b1f-4365-a321-541723926b1d.webp
749 ms
f4b0836a-ef23-4a2e-8ed2-82961bff7a52.webp
738 ms
fa275cff-3115-425e-bb8d-989337bc0a00.webp
823 ms
b197f4d5-9098-44a0-ae7f-3b07ced22c01.webp
828 ms
fa-brands-400.ttf
99 ms
fa-solid-900.ttf
129 ms
fa-regular-400.ttf
100 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
22 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
83 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
100 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
105 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
131 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
131 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
131 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
131 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
131 ms
9bac1e6f-ec2c-4e32-9acd-0ebeda4da19a.webp
809 ms
138754e5-e64a-4a3b-865c-57a00304ffce.png
813 ms
d3fec494-be5e-45f6-ade7-b0a28eb0f51e.png
809 ms
froogaloop2.min.js
805 ms
iframe_api
143 ms
js
110 ms
fc8bee03-411e-476f-9e84-6d2681cdf7bd.png
766 ms
636a595b-7e76-4bd3-86ca-ac1988ccc4a0.png
758 ms
www-widgetapi.js
4 ms
5424b045-f03e-4dc2-82e4-5e3ede53bedd.png
700 ms
bg.png
812 ms
app1.png
661 ms
app2.png
658 ms
bullet-16-16-0.png
697 ms
arrows-42-60-0.png
696 ms
kasih.com accessibility score
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
kasih.com 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
Browser errors were logged to the console
kasih.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kasih.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 Kasih.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.
kasih.com
Open Graph data is detected on the main page of Kasih. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: