Tools & Wizards About Us
pregnant2day.co.za screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

pregnant2day.co.za

Pregnant2day has all the information you want to know.

Page Load Speed

3.8 sec in total

First Response

895 ms

Resources Loaded

2.6 sec

Page Rendered

297 ms

pregnant2day.co.za screenshot

About Website

Click here to check amazing Pregnant2day content for South Africa. Otherwise, check out these important facts you probably never knew about pregnant2day.co.za

Pregnant2day, Liz and Ariel, are a dedicated team informing pregnant ladies about the journey they are embarking on.

Visit pregnant2day.co.za

Key Findings

We analyzed Pregnant2day.co.za page load time and found that the first response time was 895 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

pregnant2day.co.za performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,400 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.367

29/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

pregnant2day.co.za

895 ms

typo.css

90 ms

system.css

67 ms

general.css

64 ms

ja.tabs.css

66 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 42% of them (44 requests) were addressed to the original Pregnant2day.co.za, 10% (10 requests) were made to Google.com and 9% (9 requests) were made to D234qeqk649blg.cloudfront.net. The less responsive or slowest element that took the longest time to load (895 ms) belongs to the original domain Pregnant2day.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 599.4 kB (41%)

Content Size

1.4 MB

After Optimization

850.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pregnant2day.co.za main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 627.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 69.8 kB

  • Original 86.9 kB
  • After minification 84.2 kB
  • After compression 17.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 69.8 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 46.1 kB

  • Original 627.5 kB
  • After minification 581.3 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. Pregnant2day images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 386.2 kB

  • Original 617.0 kB
  • After minification 571.7 kB
  • After compression 230.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 386.2 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 97.2 kB

  • Original 118.3 kB
  • After minification 93.1 kB
  • After compression 21.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. Pregnant2day.co.za needs all CSS files to be minified and compressed as it can save up to 97.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (59%)

Requests Now

100

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pregnant2day.co.za

pregnant2day.co.za

895 ms

typo.css

typo.css

90 ms

system.css

system.css

67 ms

general.css

general.css

64 ms

ja.tabs.css

ja.tabs.css

66 ms

phocadownload.css

phocadownload.css

64 ms

css3.css

css3.css

66 ms

addons.css

addons.css

94 ms

layout.css

layout.css

92 ms

template.css

template.css

94 ms

usertools.css

usertools.css

95 ms

mega.css

mega.css

95 ms

typo.css

typo.css

117 ms

css3.css

css3.css

120 ms

template.css

template.css

123 ms

mega.css

mega.css

122 ms

mootools.js

mootools.js

203 ms

core.js

core.js

125 ms

mega.js

mega.js

145 ms

caption.js

caption.js

149 ms

ja.tabs.js

ja.tabs.js

150 ms

show_ads.js

show_ads.js

29 ms

plusone.js

plusone.js

66 ms

top_up-min.js

top_up-min.js

34 ms

jsapi

jsapi

42 ms

all.js

all.js

74 ms

arrow-10x10.png

arrow-10x10.png

42 ms

mainnav-bg.png

mainnav-bg.png

43 ms

navtab-l.png

navtab-l.png

43 ms

navtab-r.png

navtab-r.png

42 ms

arrow5.png

arrow5.png

45 ms

logo.png

logo.png

156 ms

rss20.gif

rss20.gif

43 ms

dissecting-humour-homepage1.jpg

dissecting-humour-homepage1.jpg

188 ms

pregnancy_banner.gif

pregnancy_banner.gif

152 ms

reg.png

reg.png

151 ms

facebook-logo.png

facebook-logo.png

153 ms

twitter-logo.png

twitter-logo.png

154 ms

4akid%20logo%20newsmall.jpg

4akid%20logo%20newsmall.jpg

156 ms

goodnight2.jpg

goodnight2.jpg

172 ms

fatima.jpg

fatima.jpg

154 ms

discovery-slides01.jpg

discovery-slides01.jpg

188 ms

discovery-slides00%20copy.jpg

discovery-slides00%20copy.jpg

232 ms

babysmall.gif

babysmall.gif

158 ms

lifesmall.gif

lifesmall.gif

171 ms

explore2daylogo.gif

explore2daylogo.gif

170 ms

acta-ad.gif

acta-ad.gif

205 ms

cpr-advert.gif

cpr-advert.gif

248 ms

zrt_lookup.html

zrt_lookup.html

37 ms

show_ads_impl.js

show_ads_impl.js

45 ms

ads

ads

258 ms

osd.js

osd.js

58 ms

ads

ads

286 ms

button-bg.gif

button-bg.gif

57 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

all.js

all.js

81 ms

ads

ads

279 ms

15 ms

default+en.css

default+en.css

4 ms

default.css

default.css

19 ms

default+en.I.js

default+en.I.js

13 ms

default.css

default.css

32 ms

m_js_controller.js

m_js_controller.js

73 ms

abg.js

abg.js

157 ms

bullet.png

bullet.png

171 ms

ga.js

ga.js

24 ms

afr.php

afr.php

173 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

186 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

126 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

100 ms

fastbutton

fastbutton

211 ms

loader.gif

loader.gif

166 ms

__utm.gif

__utm.gif

105 ms

s

s

71 ms

x_button_blue2.png

x_button_blue2.png

58 ms

redir.html

redir.html

647 ms

17347473041425952221

17347473041425952221

72 ms

subaru_oem_2016_wrx_320x50.html

subaru_oem_2016_wrx_320x50.html

54 ms

postmessageRelay

postmessageRelay

46 ms

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js

7 ms

adUtils.js

adUtils.js

10 ms

edge.6.0.0.min.js

edge.6.0.0.min.js

43 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

26 ms

rpc:shindig_random.js

rpc:shindig_random.js

42 ms

subaru_oem_2016_wrx_320x50_edge.js

subaru_oem_2016_wrx_320x50_edge.js

17 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

16 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

13 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

51 ms

subaru_oem_2016_wrx_320x50_edge.js

subaru_oem_2016_wrx_320x50_edge.js

12 ms

TweenMax.min.js

TweenMax.min.js

38 ms

TweenMax.min.js

TweenMax.min.js

38 ms

subieLogo.jpg

subieLogo.jpg

33 ms

wrx1.png

wrx1.png

12 ms

wrx2-320x50.jpg

wrx2-320x50.jpg

14 ms

default_preroll_320x50.jpg

default_preroll_320x50.jpg

16 ms

closeBtn.svg

closeBtn.svg

17 ms

async-ads.js

async-ads.js

61 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

52 ms

small-logo.png

small-logo.png

34 ms

search_box_icon.png

search_box_icon.png

34 ms

clear.png

clear.png

52 ms

iframe.html

iframe.html

148 ms

ui

ui

59 ms

Accessibility Review

pregnant2day.co.za accessibility score

67

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-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

pregnant2day.co.za best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pregnant2day.co.za SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Pregnant2day.co.za 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 Pregnant2day.co.za 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

pregnant2day.co.za

Open Graph description is not detected on the main page of Pregnant2day. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: