26.4 sec in total
42 ms
15 sec
11.4 sec
Click here to check amazing Journal Uii content for Indonesia. Otherwise, check out these important facts you probably never knew about journal.uii.ac.id
Visit journal.uii.ac.idWe analyzed Journal.uii.ac.id page load time and found that the first response time was 42 ms and then it took 26.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
journal.uii.ac.id performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value8.2 s
2/100
25%
Value21.3 s
0/100
10%
Value210 ms
88/100
30%
Value0.004
100/100
15%
Value47.0 s
0/100
10%
42 ms
5422 ms
822 ms
1349 ms
35 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 85% of them (77 requests) were addressed to the original Journal.uii.ac.id, 7% (6 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Journal.uii.ac.id.
Page size can be reduced by 1.7 MB (10%)
17.1 MB
15.4 MB
In fact, the total size of Journal.uii.ac.id main page is 17.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 16.9 MB which makes up the majority of the site volume.
Potential reduce by 73.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 73.2 kB or 85% of the original size.
Potential reduce by 1.6 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. Journal Uii images are well optimized though.
Potential reduce by 51 B
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 145 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. Journal.uii.ac.id has all CSS files already compressed.
Number of requests can be reduced by 19 (23%)
82
63
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Journal Uii. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
journal.uii.ac.id
42 ms
journal.uii.ac.id
5422 ms
red.css
822 ms
css
1349 ms
slick.min.css
35 ms
slick-theme.min.css
43 ms
css
48 ms
font-awesome.css
44 ms
css
1083 ms
academic_pro.min.css
876 ms
mobile_responsive.css
865 ms
pageHeaderTitleImage_en_US.png
870 ms
cover-0488df8c7c5afac2556b20770d4f69a5.jpg
833 ms
journalThumbnail_en_US.png
1761 ms
journalThumbnail_en_US.jpg
1763 ms
journalThumbnail_en_US.jpg
2201 ms
journalThumbnail_en_US.gif
1765 ms
journalThumbnail_en_US.jpg
1903 ms
journalThumbnail_en_US.png
2969 ms
journalThumbnail_en_US.jpg
1761 ms
journalThumbnail_en_US.png
1765 ms
journalThumbnail_en_US.jpg
2560 ms
journalThumbnail_en_US.jpg
2559 ms
journalThumbnail_en_US.png
2556 ms
journalThumbnail_en_US.png
2742 ms
journalThumbnail_en_US.jpg
3007 ms
journalThumbnail_en_US.jpg
2575 ms
journalThumbnail_en_US.jpg
4415 ms
journalThumbnail_en_US.jpg
3419 ms
journalThumbnail_en_US.png
2881 ms
journalThumbnail_en_US.png
3601 ms
journalThumbnail_en_US.jpg
2900 ms
journalThumbnail_en_US.png
2921 ms
journalThumbnail_en_US.png
3752 ms
journalThumbnail_en_US.jpg
3819 ms
journalThumbnail_en_US.jpg
5444 ms
journalThumbnail_en_US.jpg
4298 ms
journalThumbnail_en_US.jpg
4447 ms
journalThumbnail_en_US.jpg
3777 ms
journalThumbnail_en_US.jpg
3803 ms
journalThumbnail_en_US.jpg
3821 ms
slick.min.js
40 ms
jquery.min.js
3833 ms
jquery-ui.min.js
4411 ms
jquery.tag-it.js
3842 ms
bootstrap.min.js
4280 ms
readmore.min.js
3567 ms
css
19 ms
jats.toc.min.js
3580 ms
sticky.min.js
4228 ms
css
19 ms
app.js
3125 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
48 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
151 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
176 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
178 ms
u-440qyriQwlOrhSvowK_l5-fCZJ.ttf
176 ms
fontawesome-webfont.woff
18 ms
0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf
176 ms
journalThumbnail_en_US.jpg
3813 ms
journalThumbnail_en_US.jpg
3729 ms
journalThumbnail_en_US.png
4228 ms
journalThumbnail_en_US.jpg
3497 ms
journalThumbnail_en_US.jpg
3532 ms
journalThumbnail_en_US.jpg
3415 ms
journalThumbnail_en_US.jpg
5588 ms
journalThumbnail_en_US.jpg
2778 ms
journalThumbnail_en_US.jpg
2795 ms
journalThumbnail_en_US.png
2812 ms
journalThumbnail_en_US.jpg
2816 ms
journalThumbnail_en_US.jpg
2664 ms
journalThumbnail_en_US.jpg
2545 ms
journalThumbnail_en_US.png
3376 ms
journalThumbnail_en_US.jpg
3357 ms
journalThumbnail_en_US.jpg
3887 ms
journalThumbnail_en_US.png
3446 ms
journalThumbnail_en_US.jpg
3395 ms
journalThumbnail_en_US.png
3533 ms
journalThumbnail_en_US.jpg
3368 ms
journalThumbnail_en_US.jpg
3522 ms
journalThumbnail_en_US.jpg
3845 ms
journalThumbnail_en_US.jpg
4906 ms
journalThumbnail_en_US.jpg
4385 ms
journalThumbnail_en_US.png
4120 ms
journalThumbnail_en_US.jpg
5202 ms
journalThumbnail_en_US.png
4074 ms
journalThumbnail_en_US.jpg
4178 ms
journalThumbnail_en_US.jpg
3543 ms
headershadow.png
4405 ms
footer_bg.png
4577 ms
main.js
13 ms
journal.uii.ac.id 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 are not valid or misspelled
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
journal.uii.ac.id 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
journal.uii.ac.id SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Journal.uii.ac.id 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 Journal.uii.ac.id 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.
journal.uii.ac.id
Open Graph description is not detected on the main page of Journal Uii. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: