Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nepsmar.com

nepsmar.com has expired

Page Load Speed

4.1 sec in total

First Response

297 ms

Resources Loaded

2.2 sec

Page Rendered

1.6 sec

About Website

Visit nepsmar.com now to see the best up-to-date Nepsmar content and also check out these interesting facts you probably never knew about nepsmar.com

NEPSMAR est une entreprise Marocaine leader dans la sécurité incendie et la survie maritime. Notre large éventail d’offres s’appuie sur trois pôles métiers complémentaires : l’inspection et la mainten...

Visit nepsmar.com

Key Findings

We analyzed Nepsmar.com page load time and found that the first response time was 297 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

nepsmar.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value16.0 s

0/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.052

99/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

297 ms

bootstrap.min.css

129 ms

magnific-popup.min.css

88 ms

icon-font.min.css

93 ms

fontawesome-webfont.min.css

105 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 78% of them (39 requests) were addressed to the original Nepsmar.com, 10% (5 requests) were made to Maps.google.com and 4% (2 requests) were made to Cdn.linearicons.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Nepsmar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 610.7 kB (15%)

Content Size

4.0 MB

After Optimization

3.4 MB

In fact, the total size of Nepsmar.com main page is 4.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 24.5 kB

  • Original 31.7 kB
  • After minification 28.3 kB
  • After compression 7.2 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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.5 kB or 77% of the original size.

Image Optimization

-13%

Potential reduce by 475.7 kB

  • Original 3.7 MB
  • After minification 3.2 MB

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, Nepsmar needs image optimization as it can save up to 475.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-44%

Potential reduce by 107.5 kB

  • Original 244.3 kB
  • After minification 243.9 kB
  • After compression 136.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 107.5 kB or 44% of the original size.

CSS Optimization

-9%

Potential reduce by 2.9 kB

  • Original 33.8 kB
  • After minification 33.7 kB
  • After compression 31.0 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Nepsmar.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (66%)

Requests Now

44

After Optimization

15

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

Accessibility Review

nepsmar.com accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

nepsmar.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nepsmar.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nepsmar.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Nepsmar.com 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

Open Graph data is detected on the main page of Nepsmar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: