Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

niniban.com

نی‌نی‌بان، راهنمای بارداری و کودکیاری

Page Load Speed

8.5 sec in total

First Response

557 ms

Resources Loaded

6.7 sec

Page Rendered

1.2 sec

About Website

Welcome to niniban.com homepage info - get ready to check Niniban best content for Iran right away, or after learning these important things about niniban.com

نی‌ نی‌ بان، راهنمای بارداری و کودک‌ یاری - بارداری هفته به هفته - مشاوره رایگان

Visit niniban.com

Key Findings

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

Performance Metrics

niniban.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value1,130 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

niniban.com

557 ms

niniban.com

1233 ms

main_rtl.css

1095 ms

frameworks.min.js

1441 ms

lang-fa.min.js

955 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 25% of them (20 requests) were addressed to the original Niniban.com, 60% (49 requests) were made to Cdn.niniban.com and 7% (6 requests) were made to Assets.niniban.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Trustseal.e-rasaneh.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 294.1 kB (38%)

Content Size

763.9 kB

After Optimization

469.9 kB

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

HTML Optimization

-89%

Potential reduce by 254.3 kB

  • Original 285.2 kB
  • After minification 232.5 kB
  • After compression 30.9 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 52.7 kB, which is 18% 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 254.3 kB or 89% of the original size.

Image Optimization

-8%

Potential reduce by 39.6 kB

  • Original 477.0 kB
  • After minification 437.4 kB

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. Niniban images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 142 B

  • Original 1.8 kB
  • After minification 1.8 kB
  • After compression 1.6 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 5 (6%)

Requests Now

77

After Optimization

72

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

Accessibility Review

niniban.com accessibility score

87

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-hidden="true"] elements contain focusable descendents

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

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

niniban.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

niniban.com SEO score

98

Search Engine Optimization Advices

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

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Niniban.com can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Niniban.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 Niniban. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: