Tools & Wizards About Us
rajasmem.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

rajasmem.com

Your domain is expired

Page Load Speed

10.4 sec in total

First Response

444 ms

Resources Loaded

9.5 sec

Page Rendered

406 ms

rajasmem.com screenshot

About Website

Click here to check amazing Rajasmem content. Otherwise, check out these important facts you probably never knew about rajasmem.com

Domain is expired

Visit rajasmem.com

Key Findings

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

Performance Metrics

rajasmem.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

rajasmem.com

444 ms

rajasmem.com

3320 ms

frontend-lite.min.css

278 ms

general.min.css

481 ms

eael-1174.css

601 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 88% of them (91 requests) were addressed to the original Rajasmem.com, 12% (12 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Rajasmem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 304.2 kB (17%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rajasmem.com main page is 1.8 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. 55% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 167.2 kB

  • Original 193.9 kB
  • After minification 191.0 kB
  • After compression 26.7 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 167.2 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 5.2 kB

  • Original 1.0 MB
  • After minification 1.0 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. Rajasmem images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 107.6 kB

  • Original 339.9 kB
  • After minification 309.4 kB
  • After compression 232.3 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.6 kB or 32% of the original size.

CSS Optimization

-13%

Potential reduce by 24.2 kB

  • Original 180.0 kB
  • After minification 170.4 kB
  • After compression 155.8 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. Rajasmem.com needs all CSS files to be minified and compressed as it can save up to 24.2 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 84 (93%)

Requests Now

90

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rajasmem.com

rajasmem.com

444 ms

rajasmem.com

rajasmem.com

3320 ms

frontend-lite.min.css

frontend-lite.min.css

278 ms

general.min.css

general.min.css

481 ms

eael-1174.css

eael-1174.css

601 ms

styles.css

styles.css

609 ms

em-front-common-utility.css

em-front-common-utility.css

606 ms

ep-material-fonts-icon.css

ep-material-fonts-icon.css

608 ms

jquery.toast.min.css

jquery.toast.min.css

619 ms

font-awesome.min.css

font-awesome.min.css

674 ms

to-top-public.css

to-top-public.css

798 ms

frontend-lite.min.css

frontend-lite.min.css

806 ms

swiper.min.css

swiper.min.css

812 ms

post-5.css

post-5.css

809 ms

sticky.css

sticky.css

824 ms

global.css

global.css

867 ms

post-10.css

post-10.css

996 ms

frontend.css

frontend.css

1007 ms

header-footer-elementor.css

header-footer-elementor.css

1013 ms

post-1617.css

post-1617.css

1036 ms

style-main-new.min.css

style-main-new.min.css

1044 ms

post-1174.css

post-1174.css

1059 ms

post-1444.css

post-1444.css

1193 ms

fontawesome.css

fontawesome.css

1207 ms

nav-menu.css

nav-menu.css

1214 ms

search.css

search.css

1236 ms

style.css

style.css

1247 ms

cart-icon.css

cart-icon.css

1252 ms

ionicons.css

ionicons.css

1391 ms

awesome.css

awesome.css

1408 ms

bootstrap.css

bootstrap.css

1623 ms

bootstrap-theme.css

bootstrap-theme.css

1436 ms

wpbc-tippy-popover.css

wpbc-tippy-popover.css

1459 ms

wpbc-tippy-times.css

wpbc-tippy-times.css

1445 ms

material-design-icons.css

material-design-icons.css

1791 ms

wpbc_time-selector.css

wpbc_time-selector.css

1607 ms

grey.css

grey.css

1637 ms

css

css

29 ms

client.css

client.css

1634 ms

calendar.css

calendar.css

1393 ms

green-01.css

green-01.css

1340 ms

timeline_v2.css

timeline_v2.css

1235 ms

timeline_skin_v2.css

timeline_skin_v2.css

1242 ms

widget-icon-list.min.css

widget-icon-list.min.css

1237 ms

elementor-icons.min.css

elementor-icons.min.css

1275 ms

animations.min.css

animations.min.css

1383 ms

jquery.min.js

jquery.min.js

1390 ms

jquery-migrate.min.js

jquery-migrate.min.js

1473 ms

jquery.toast.min.js

jquery.toast.min.js

1276 ms

toast-message.js

toast-message.js

1458 ms

ep-common-script.js

ep-common-script.js

1464 ms

to-top-public.js

to-top-public.js

1378 ms

sticky.min.js

sticky.min.js

1397 ms

wpbc_vars.js

wpbc_vars.js

1278 ms

popper.js

popper.js

1391 ms

tippy-bundle.umd.js

tippy-bundle.umd.js

1454 ms

jquery.datepick.wpbc.9.0.js

jquery.datepick.wpbc.9.0.js

1634 ms

wpbc_all.js

wpbc_all.js

1643 ms

client.js

client.js

1427 ms

create_booking.js

create_booking.js

1277 ms

wpbc_times.js

wpbc_times.js

1388 ms

wpbc_time-selector.js

wpbc_time-selector.js

1452 ms

timeline_v2.js

timeline_v2.js

1428 ms

general.min.js

general.min.js

1530 ms

eael-1174.js

eael-1174.js

1547 ms

index.js

index.js

1472 ms

index.js

index.js

1456 ms

frontend.js

frontend.js

1432 ms

underscore-before.js

underscore-before.js

1444 ms

underscore.min.js

underscore.min.js

1438 ms

underscore-after.js

underscore-after.js

1390 ms

wp-util.min.js

wp-util.min.js

1415 ms

imagesloaded.min.js

imagesloaded.min.js

1428 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1431 ms

webpack.runtime.min.js

webpack.runtime.min.js

1425 ms

frontend-modules.min.js

frontend-modules.min.js

1309 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1390 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1418 ms

wp-polyfill.min.js

wp-polyfill.min.js

1435 ms

hooks.min.js

hooks.min.js

1438 ms

i18n.min.js

i18n.min.js

1421 ms

frontend.min.js

frontend.min.js

1321 ms

waypoints.min.js

waypoints.min.js

1332 ms

core.min.js

core.min.js

1368 ms

frontend.min.js

frontend.min.js

1278 ms

elements-handlers.min.js

elements-handlers.min.js

1221 ms

jquery.sticky.min.js

jquery.sticky.min.js

1243 ms

frontend.min.js

frontend.min.js

1258 ms

rajas-logo-2.png

rajas-logo-2.png

1081 ms

banner.jpg

banner.jpg

3049 ms

tools-image-1536x782.jpg

tools-image-1536x782.jpg

1158 ms

banner-10.jpg

banner-10.jpg

1769 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

32 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

54 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

55 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

54 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

55 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

55 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

56 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

56 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

55 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

57 ms

Accessibility Review

rajasmem.com accessibility score

96

Accessibility Issues

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

rajasmem.com best practices score

92

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

Page has valid source maps

SEO Factors

rajasmem.com SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

rajasmem.com

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