6.6 sec in total
583 ms
5.6 sec
363 ms
Welcome to tilljannah.my homepage info - get ready to check Tilljannah best content for Malaysia right away, or after learning these important things about tilljannah.my
Masih single dan ingin berkahwin? Jom sertai TillJannah.my, sebuah platform cari jodoh muslim untuk anda bertemu calon pasangan yang anda idamkan.
Visit tilljannah.myWe analyzed Tilljannah.my page load time and found that the first response time was 583 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tilljannah.my performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value55.4 s
0/100
25%
Value37.6 s
0/100
10%
Value18,250 ms
0/100
30%
Value0.087
93/100
15%
Value46.1 s
0/100
10%
583 ms
1673 ms
115 ms
562 ms
750 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 43% of them (23 requests) were addressed to the original Tilljannah.my, 15% (8 requests) were made to Embed.tawk.to and 7% (4 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tilljannah.my.
Page size can be reduced by 166.8 kB (18%)
940.4 kB
773.6 kB
In fact, the total size of Tilljannah.my main page is 940.4 kB. 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 743.7 kB which makes up the majority of the site volume.
Potential reduce by 39.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. This page needs HTML code to be minified as it can gain 9.1 kB, which is 19% 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 39.0 kB or 80% of the original size.
Potential reduce by 112.7 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. Obviously, Tilljannah needs image optimization as it can save up to 112.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 15.0 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 15.0 kB or 12% of the original size.
Potential reduce by 84 B
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. Tilljannah.my has all CSS files already compressed.
Number of requests can be reduced by 25 (49%)
51
26
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tilljannah. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
tilljannah.my
583 ms
www.tilljannah.my
1673 ms
css
115 ms
bootstrap.min.css
562 ms
font-awesome.min.css
750 ms
jquery.min.js
1056 ms
bootstrap.bundle.min.js
1184 ms
api:client.js
128 ms
js
145 ms
gtm.js
82 ms
bg_1.png
1315 ms
logo_my.png
291 ms
facebook-logo.png
538 ms
twitter-logo.png
254 ms
login-with-google.png
511 ms
1.jpg
579 ms
2.jpg
749 ms
3.jpg
792 ms
4.jpg
833 ms
5.jpg
834 ms
6.jpg
849 ms
7.jpg
996 ms
8.jpg
1054 ms
16406762961048382375.jpg
1877 ms
1640236257667889277.jpg
1616 ms
16402339641110117611.jpg
1928 ms
cb=gapi.loaded_0
62 ms
sdk.js
179 ms
default
247 ms
fbevents.js
178 ms
events.js
289 ms
fontawesome-webfont.woff
1686 ms
cb=gapi.loaded_1
147 ms
conversion_async.js
219 ms
js
114 ms
iframe
214 ms
sdk.js
68 ms
510620424164132
122 ms
analytics.js
157 ms
159 ms
78 ms
151 ms
m=base
31 ms
collect
45 ms
collect
45 ms
iframerpc
39 ms
22 ms
twk-event-polyfill.js
258 ms
twk-main.js
22 ms
twk-vendor.js
117 ms
twk-chunk-vendors.js
182 ms
twk-chunk-common.js
152 ms
twk-runtime.js
104 ms
twk-app.js
83 ms
tilljannah.my accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
tilljannah.my 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
tilljannah.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
MS
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tilljannah.my can be misinterpreted by Google and other search engines. Our service has detected that Malay is used on the page, and it does not match the claimed English language. Our system also found out that Tilljannah.my 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.
tilljannah.my
Open Graph data is detected on the main page of Tilljannah. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: