Gsb.co.zm Test Results

Gsb.co.zm Mobile Performance: 11/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Est savings of 507 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.
Avoid serving legacy JavaScript to modern browsers
Est savings of 10 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Avoid multiple page redirects
Est savings of 1,080 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
12,680 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
3.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Reduce unused CSS
Est savings of 97 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 670 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Minimize main-thread work
6.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
6 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 an excessive DOM size
1,315 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Avoid enormous network payloads
Total size was 3,275 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Use video formats for animated content
Est savings of 96 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
Serve images in next-gen formats
Est savings of 114 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.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Defer offscreen images
Est savings of 197 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.
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
Serve static assets with an efficient cache policy
95 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Max Potential First Input Delay
1,270 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.
Document request latency
Est savings of 130 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Legacy JavaScript
Est savings of 9 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Use efficient cache lifetimes
Est savings of 1,123 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Time to Interactive
25.0 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.
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Improve image delivery
Est savings of 321 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Gsb.co.zm Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Gsb.co.zm Mobile Best Practices: 55/100
Quick overview:
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
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
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Gsb.co.zm Mobile Accessibility: 85/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.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Tables do not use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `colspan]` attribute may improve the experience for screen reader users. [Learn more about captions.
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.
Similar sites
Similar tests
www.gsb.com
www.gsb.net
www.gsb.org
www.gsb.info
www.gsb.biz
www.gsb.us
www.gsb.mobi
www.sb.co.zm
www.gsb.co.zm
www.fsb.co.zm
www.gfsb.co.zm
www.fgsb.co.zm
www.vsb.co.zm
www.gvsb.co.zm
www.vgsb.co.zm
www.tsb.co.zm
www.gtsb.co.zm
www.tgsb.co.zm
www.bsb.co.zm
www.gbsb.co.zm
www.bgsb.co.zm
www.ysb.co.zm
www.gysb.co.zm
www.ygsb.co.zm
www.hsb.co.zm
www.ghsb.co.zm
www.hgsb.co.zm
www.gb.co.zm
www.gwb.co.zm
www.gswb.co.zm
www.gwsb.co.zm
www.geb.co.zm
www.gseb.co.zm
www.gesb.co.zm
www.gdb.co.zm
www.gsdb.co.zm
www.gdsb.co.zm
www.gzb.co.zm
www.gszb.co.zm
www.gzsb.co.zm
www.gxb.co.zm
www.gsxb.co.zm
www.gxsb.co.zm
www.gab.co.zm
www.gsab.co.zm
www.gasb.co.zm
www.gs.co.zm
www.gsv.co.zm
www.gsbv.co.zm
www.gsvb.co.zm
www.gsg.co.zm
www.gsbg.co.zm
www.gsgb.co.zm
www.gsh.co.zm
www.gsbh.co.zm
www.gshb.co.zm
www.gsn.co.zm
www.gsbn.co.zm
www.gsnb.co.zm
Last Tested: