Merudi.net Test Results

Merudi.net Mobile Performance: 38/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minify CSS
Potential savings of 110 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Reduce unused JavaScript
Potential savings of 523 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Minify JavaScript
Potential savings of 52 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Reduce unused CSS
Potential savings of 547 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Efficiently encode images
Potential savings of 7 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Enable text compression
Potential savings of 1,086 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Preload Largest Contentful Paint image
Potential savings of 600 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Serve images in next-gen formats
Potential savings of 52 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Largest Contentful Paint element
11,570 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minimize main-thread work
2.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid large layout shifts
3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Serve static assets with an efficient cache policy
38 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Avoid serving legacy JavaScript to modern browsers
Potential savings of 1 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Properly size images
Potential savings of 5 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Defer offscreen images
Potential savings of 41 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Time to Interactive
12.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
6.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Merudi.net Mobile SEO: 100/100
Quick overview:

Merudi.net Mobile Best Practices: 48/100
Quick overview:
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Document doesn't use legible font sizes
42.76% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Merudi.net Mobile Accessibility: 71/100
Quick overview:
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Similar tests
www.merudi.com
www.merudi.net
www.merudi.org
www.merudi.info
www.merudi.biz
www.merudi.us
www.merudi.mobi
www.erudi.net
www.merudi.net
www.nerudi.net
www.mnerudi.net
www.nmerudi.net
www.jerudi.net
www.mjerudi.net
www.jmerudi.net
www.kerudi.net
www.mkerudi.net
www.kmerudi.net
www.mrudi.net
www.mwrudi.net
www.mewrudi.net
www.mwerudi.net
www.msrudi.net
www.mesrudi.net
www.mserudi.net
www.mdrudi.net
www.medrudi.net
www.mderudi.net
www.mrrudi.net
www.merrudi.net
www.mrerudi.net
www.meudi.net
www.meeudi.net
www.mereudi.net
www.meerudi.net
www.medudi.net
www.merdudi.net
www.mefudi.net
www.merfudi.net
www.mefrudi.net
www.metudi.net
www.mertudi.net
www.metrudi.net
www.merdi.net
www.merydi.net
www.meruydi.net
www.meryudi.net
www.merhdi.net
www.meruhdi.net
www.merhudi.net
www.merjdi.net
www.merujdi.net
www.merjudi.net
www.meridi.net
www.meruidi.net
www.meriudi.net
www.merui.net
www.meruxi.net
www.merudxi.net
www.meruxdi.net
www.merusi.net
www.merudsi.net
www.merusdi.net
www.meruei.net
www.merudei.net
www.meruedi.net
www.meruri.net
www.merudri.net
www.merurdi.net
www.merufi.net
www.merudfi.net
www.merufdi.net
www.meruci.net
www.merudci.net
www.merucdi.net
www.merud.net
www.merudu.net
www.merudiu.net
www.merudui.net
www.merudj.net
www.merudij.net
www.merudji.net
www.merudk.net
www.merudik.net
www.merudki.net
www.merudo.net
www.merudio.net
www.merudoi.net
Last Tested: