Tools & Wizards About Us
jobs.id screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

jobs.id

Situs Lowongan Kerja Indonesia | Karir.com

Page Load Speed

7.4 sec in total

First Response

1.1 sec

Resources Loaded

5.9 sec

Page Rendered

389 ms

jobs.id screenshot

About Website

Click here to check amazing Jobs content for Indonesia. Otherwise, check out these important facts you probably never knew about jobs.id

Visit jobs.id

Key Findings

We analyzed Jobs.id page load time and found that the first response time was 1.1 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

jobs.id performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value800 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.894

3/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

karir.com

1094 ms

gtm.js

55 ms

c0fe2f68bea2c7881375.css

254 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

759 ms

webpack-0d40d15c8b55ab93cefc.js

751 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Jobs.id, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Karir.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.6 kB (30%)

Content Size

796.8 kB

After Optimization

559.2 kB

  • HTML
  • Images

In fact, the total size of Jobs.id main page is 796.8 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. 45% of websites need less resources to load. Images take 673.6 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 112.7 kB

  • Original 123.2 kB
  • After minification 123.2 kB
  • After compression 10.5 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 112.7 kB or 91% of the original size.

Image Optimization

-19%

Potential reduce by 125.0 kB

  • Original 673.6 kB
  • After minification 548.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, Jobs needs image optimization as it can save up to 125.0 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 37 (74%)

Requests Now

50

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jobs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

karir.com

karir.com

1094 ms

gtm.js

gtm.js

55 ms

c0fe2f68bea2c7881375.css

c0fe2f68bea2c7881375.css

254 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

759 ms

webpack-0d40d15c8b55ab93cefc.js

webpack-0d40d15c8b55ab93cefc.js

751 ms

framework-4e61e9627bbe77f78d75.js

framework-4e61e9627bbe77f78d75.js

1265 ms

main-e6cc170eb3206e037f22.js

main-e6cc170eb3206e037f22.js

1029 ms

_app-834b9741571eed8bb851.js

_app-834b9741571eed8bb851.js

1033 ms

75fc9c18-2e1fec015f3211e6fdf5.js

75fc9c18-2e1fec015f3211e6fdf5.js

1035 ms

7125-444cbb7fa7456773085e.js

7125-444cbb7fa7456773085e.js

1001 ms

7670-a3e5eab59e5bcaaa11cf.js

7670-a3e5eab59e5bcaaa11cf.js

1010 ms

8973-b6e87c048e8b741f82a2.js

8973-b6e87c048e8b741f82a2.js

1253 ms

539-f60a82ec5ce3db453761.js

539-f60a82ec5ce3db453761.js

1263 ms

2739-7d1632b623acf0849a08.js

2739-7d1632b623acf0849a08.js

1295 ms

5522-a8bf0c902b561f4e434e.js

5522-a8bf0c902b561f4e434e.js

1296 ms

4388-99a6dcb243cc7f10b7c2.js

4388-99a6dcb243cc7f10b7c2.js

1297 ms

8006-d2ecb50227454b7aac64.js

8006-d2ecb50227454b7aac64.js

1755 ms

139-494fed5c77d25e50ad6f.js

139-494fed5c77d25e50ad6f.js

1513 ms

3446-05fe48f0409797ed5f68.js

3446-05fe48f0409797ed5f68.js

1518 ms

8473-c04d23604e512304ee2d.js

8473-c04d23604e512304ee2d.js

1542 ms

8361-804296b5ad464f998ef2.js

8361-804296b5ad464f998ef2.js

1551 ms

2553-2d89aaf52d2e47e7bcc3.js

2553-2d89aaf52d2e47e7bcc3.js

1552 ms

9830-35d12bf551ee6cb93ab9.js

9830-35d12bf551ee6cb93ab9.js

1765 ms

2872-c0e6eb408cc3d163ba0a.js

2872-c0e6eb408cc3d163ba0a.js

1771 ms

6388-9ee30dcb7c82e8bfbbbe.js

6388-9ee30dcb7c82e8bfbbbe.js

1801 ms

1123-e43f8cfc057789abc45d.js

1123-e43f8cfc057789abc45d.js

1812 ms

7294-efdcae61786f05ce7d8a.js

7294-efdcae61786f05ce7d8a.js

1815 ms

8939-2d8cd93e89ee8020545c.js

8939-2d8cd93e89ee8020545c.js

2008 ms

8373-796f7e4214a909475204.js

8373-796f7e4214a909475204.js

2017 ms

5809-af2edb5dfd5a37516d92.js

5809-af2edb5dfd5a37516d92.js

2022 ms

8200-aa32b32a08cece755fcc.js

8200-aa32b32a08cece755fcc.js

2057 ms

4723-37ad0c9342099e08bc4f.js

4723-37ad0c9342099e08bc4f.js

2070 ms

2012-b27a8bc6e80bea46d2fd.js

2012-b27a8bc6e80bea46d2fd.js

2073 ms

1267-1ee7d699ff02723c77d8.js

1267-1ee7d699ff02723c77d8.js

2259 ms

693-7a50a38c7278b7a7d357.js

693-7a50a38c7278b7a7d357.js

2270 ms

3651-a6a86c4ad4fcba8d50e8.js

3651-a6a86c4ad4fcba8d50e8.js

2275 ms

9692-35df134b605d04475463.js

9692-35df134b605d04475463.js

2313 ms

index-224f0246b0346a4231c1.js

index-224f0246b0346a4231c1.js

2332 ms

_buildManifest.js

_buildManifest.js

2032 ms

_ssgManifest.js

_ssgManifest.js

1765 ms

MuseoSans_700.ttf

MuseoSans_700.ttf

1756 ms

MuseoSans_900.ttf

MuseoSans_900.ttf

1545 ms

MuseoSans_500.ttf

MuseoSans_500.ttf

1823 ms

MuseoSans_300.ttf

MuseoSans_300.ttf

1827 ms

default.png

default.png

1571 ms

1.png

1.png

1732 ms

2.png

2.png

1529 ms

3.png

3.png

1524 ms

4.png

4.png

1571 ms

1.png

1.png

1970 ms

Karir%20Care.png

Karir%20Care.png

1736 ms

Background%20Homepage.png

Background%20Homepage.png

1742 ms

Background%20Peta.png

Background%20Peta.png

2086 ms

Light%20Blue%20Desktop.png

Light%20Blue%20Desktop.png

2366 ms

Empty%20Opportunities%202.png

Empty%20Opportunities%202.png

1577 ms

Accessibility Review

jobs.id accessibility score

70

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jobs.id best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

jobs.id SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ID

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jobs.id can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jobs.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.

Social Sharing Optimization

jobs.id

Open Graph description is not detected on the main page of Jobs. 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: