Login

Automated Report

juandisay.org

Generated on October 1, 2025 · Domain: juandisay.org

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis
Favicon
juandisay.org
2025/10/01
76

Overall Score

97

PageSpeed

57

Website Quality

75

Trust & Security

97

Performance

100

SEO

100

Best Practices

91

Accessibility

Performance
97/100
Largest Contentful Paint
24/25
2.2s
2.5s4.0s
First Contentful Paint
10/10
1.2s
1.8s3.0s
Total Blocking Time
30/30
7ms
200ms400ms
Cumulative Layout Shift
25/25
0.00
0.100.25
Speed Index
8/10
3.8s
3.4s5.4s
SEO
100/100
Page isn’t blocked from indexing
37/37
Document has a `<title>` element
9/9
Document has a meta description
9/9
Page has successful HTTP status code
9/9
Links have descriptive text
9/9
Links are crawlable
9/9
Image elements have `[alt]` attributes
9/9
Document has a valid `hreflang`
9/9
Best Practices
100/100
Uses HTTPS
18/18
Avoids deprecated APIs
18/18
Avoids third-party cookies
18/18
Allows users to paste into input fields
11/11
Avoids requesting the geolocation permission on page load
4/4
Avoids requesting the notification permission on page load
4/4
Displays images with correct aspect ratio
4/4
Serves images with appropriate resolution
4/4
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
4/4
Document uses legible font sizes
4/4
Page has the HTML doctype
4/4
Properly defines charset
4/4
No browser errors logged to the console
4/4
No issues in the `Issues` panel in Chrome Devtools
4/4
Accessibility
91/100
`[aria-*]` attributes match their roles
6/6
`[aria-hidden="true"]` is not present on the document `<body>`
6/6
`[role]`s have all required `[aria-*]` attributes
6/6
`[aria-*]` attributes have valid values
6/6
`[aria-*]` attributes are valid and not misspelled
6/6
Buttons have an accessible name
6/6
Image elements have `[alt]` attributes
6/6
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
6/6
ARIA attributes are used as specified for the element's role
4/4
Elements use only permitted ARIA attributes
4/4
`[role]` values are valid
4/4
Background and foreground colors do not have a sufficient contrast ratio.
0/4
Document has a `<title>` element
4/4
`<html>` element has a `[lang]` attribute
4/4
`<html>` element has a valid value for its `[lang]` attribute
4/4
Links do not have a discernible name
0/4
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
4/4
No element has a `[tabindex]` value greater than 0
4/4
Touch targets have sufficient size and spacing.
4/4
Heading elements appear in a sequentially-descending order
2/2
Uses ARIA roles only on compatible elements
1/1
Deprecated ARIA roles were not used
1/1
Image elements do not have `[alt]` attributes that are redundant text.
1/1

Site Quality

Title
20/20
Juandi Syafrin | Sr. Python Developer
37 chars (ideal 30–60)
Meta Description
12/15
Personal portfolio of Juandi Syafrin, a Senior Python Developer with 7+ years of experience in software development.
116 chars (ideal 120–160)
Favicon
3/3
Favicon preview
https://www.google.com/s2/favicons?domain=juandisay.org&sz=48
present
Viewport meta
8/8
width=device-width, initial-scale=1
correct (width=device-width, initial-scale=1)
robots.txt
0/6
missing (ideal: User-agent: * + Allow: / + Sitemap)
Sitemap
0/7
missing (create sitemap.xml and submit to Google Search Console)
Headings
6/6
H1Juandi Syafrin
H2Sr. Python Developer
H2About Me
H3Professional Profile
H3Skills &amp; Expertise
H4Programming Languages
H4Databases
H4Tools &amp; Technologies
H4Methodologies
H2Recent Projects
H3Bot Trade Crypto
H3Analysis and Prediction of Labs Data with LLM
H2Work Experience
H3Consultant IT | Full-Stack Developer
H3Python Back-End Developer
H3Python Back-End Developer
H2Recommendations
H3Syarif Hidayat
H3Matthew Surya
H2Juandi Syafrin
correct structure
Schema.org JSON-LD
0/2
missing (consider Organization, Article, Product, or FAQPage schemas)
Canonical URL
0/8
missing (add <link rel='canonical'> to avoid duplicate content)
HTML lang
4/4
en
present
Character encoding
4/4
utf-8
present

Open Graph

Title
0/3
missing (add <meta property='og:title'> for social sharing)
Description
0/3
missing (add <meta property='og:description'> for social sharing)
Image
0/3
missing (add <meta property='og:image'> with 1200x630px image)
URL
0/3
missing (add <meta property='og:url'> with full URL)
Type
0/1
missing (add <meta property='og:type' content='website'>)

Twitter Cards

Card Type
0/1
missing
Title
0/1
missing (add <meta name='twitter:title'> for Twitter sharing)
Description
0/1
missing (add <meta name='twitter:description'> for Twitter sharing)
Image
0/1
missing (add <meta name='twitter:image'> with 1200x630px image)

Security Headers

HTTPS
30/30
HTTPS enabled
HTTP Strict Transport Security
15/15
Strict-Transport-Security: max-age=63072000
Content Security Policy
0/15
missing (should be: Content-Security-Policy: default-src 'self')
Frame Protection
0/5
missing (should be: X-Frame-Options: SAMEORIGIN)
MIME Type Protection
0/5
missing (should be: X-Content-Type-Options: nosniff)

Domain Trust

Domain Rating
25/25
34 (Last sync: 30th July 2025)
1525
Domain Age
5/5
7 years
Registrar
CV. Rumahweb Indonesia
Country
ID

Infrastructure

Provider
Vercel

FAQs

Report-specific answers

Key takeaways for juandisay.org pulled from this audit.

How often should I refresh the YourWebsiteScore report for juandisay.org?

The latest audit was captured on October 1, 2025.

Re-run the analysis after major deployments or at least once a month so you can spot Core Web Vitals, snippet, or security regressions before they affect rankings or conversions.

Which Lighthouse performance improvements should juandisay.org tackle first?

Speed Index (mobile) at 3.8s: reclaim ≈2 points. Trim render-blocking resources, preconnect to critical domains, and focus on above-the-fold rendering to accelerate visual completion.

Largest Contentful Paint (mobile) at 2.2s: reclaim ≈1 points. Optimise hero media, inline critical CSS, and prioritise above-the-fold requests so the primary content renders faster.

Which Lighthouse SEO audits should juandisay.org fix first?

Mobile Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Desktop Lighthouse SEO is 100/100. Keep schema, robots directives, and headings tidy so the score stays maxed.

Which Lighthouse Best Practices should juandisay.org fix first?

Mobile Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.

Desktop Lighthouse Best Practices score is 100/100. Keep TLS, resource loading, and client-side APIs up-to-date to stay maxed.

Which Lighthouse Accessibility audits should juandisay.org fix first?

Background and foreground colors do not have a sufficient contrast ratio. (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make juandisay.org easier to use.

Links do not have a discernible name (mobile) is missing roughly 4 points. Fixing it will raise the Accessibility score and make juandisay.org easier to use.

Background and foreground colors do not have a sufficient contrast ratio. (desktop) is missing roughly 5 points. Fixing it will raise the Accessibility score and make juandisay.org easier to use.

Links do not have a discernible name (desktop) is missing roughly 5 points. Fixing it will raise the Accessibility score and make juandisay.org easier to use.

Which Website Quality issues should juandisay.org fix first?

Canonical URL: missing ≈8 points. Missing (add <link rel='canonical'> to avoid duplicate content). Focus on it to lift juandisay.org's Website Quality score.

Sitemap: missing ≈7 points. Missing (create sitemap.xml and submit to Google Search Console). Focus on it to lift juandisay.org's Website Quality score.

robots.txt: missing ≈6 points. Missing (ideal: User-agent: * + Allow: / + Sitemap). Focus on it to lift juandisay.org's Website Quality score.

Which Trust & Security fixes should juandisay.org tackle first?

Content Security Policy: missing ≈15 points. Missing (should be: Content-Security-Policy: default-src 'self'). Close this gap to raise juandisay.org's Trust & Security score.

Frame Protection: missing ≈5 points. Missing (should be: X-Frame-Options: SAMEORIGIN). Close this gap to raise juandisay.org's Trust & Security score.

MIME Type Protection: missing ≈5 points. Missing (should be: X-Content-Type-Options: nosniff). Close this gap to raise juandisay.org's Trust & Security score.

Instant Audit

See your site the way search engines feel it

Launch a free crawl in under 30 seconds and get a ranked hit-list of fixes that lift speed, visibility, and trust.

Start Free Analysis