modrinth.com website review

27 images could be 944 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

About 177 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 52 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

6 long tasks block the main thread while loading, the longest for 318 ms. During a long task the page ignores taps.

15 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

6 files are served with short cache lifetimes, so returning visitors download them again (77 KiB).

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

About 16 KiB of CSS is downloaded but never applied on this page.

1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 8 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.53 (75th percentile). Good is under 0.1.

Your largest element takes 30.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Discover, play, and share Minecraft content through our ope…”.

The page becomes fully interactive after 30.8 s. Good is under 3.8 s.

The first text or image appears after 6.8 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.

Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 477 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

Real visitors wait 992 ms for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 298 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 484 ms to 467 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.0 MB in 235 requests on a phone: other files 3.3 MB (116), images 1.2 MB (40) and scripts 907 KiB (56). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example thumbnail.webp at 1,920 px wide, shown at 358 px. Resized copies would save about 376 KiB.

1 image (228 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

3 images further down the page (290 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 205.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

Your title is only 8 characters: “Modrinth”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://modrinth.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 126 pages on modrinth.com and 15 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/settings is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, /discover/mods, /discover/resourcepacks, /discover/datapacks, /discover/shaders and /discover/modpacks and 2 others all use the title “Modrinth”. Search engines can't tell which page to show for a search, so each competes with the others.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example /mod/megas-arms, whose canonical is /project/pTRacP6L. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/discover/mods, /discover/resourcepacks, /discover/datapacks, /discover/shaders, /discover/modpacks and /discover/plugins and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 71 found) and read each the way a search engine does.

Large scripts ship without source maps.

1 link to other sites is dead, for example https://bsky.app/profile/modrinth.com (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://discord.modrinth.com/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

modrinth.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,764 words of visible text.

modrinth.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be modrinth.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 4 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.