Tools & Wizards About Us
namesbyorigin.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

namesbyorigin.com

One of the World’s Largest Baby Names Website, with over 1,40,000+ Baby Names

Page Load Speed

6.8 sec in total

First Response

1.3 sec

Resources Loaded

5.3 sec

Page Rendered

230 ms

namesbyorigin.com screenshot

About Website

Welcome to namesbyorigin.com homepage info - get ready to check Names Byorigin best content right away, or after learning these important things about namesbyorigin.com

Naming a baby boy or a baby girl has always been a tough job for parents. You no longer need to worry about it.

Visit namesbyorigin.com

Key Findings

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

Performance Metrics

namesbyorigin.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value9.9 s

9/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

namesbyorigin.com

1259 ms

wp-emoji-release.min.js

242 ms

bootstrap.min.css

484 ms

font-sizes.min.css

696 ms

style.min.css

706 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 49% of them (39 requests) were addressed to the original Namesbyorigin.com, 33% (26 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Namesbyorigin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.4 kB (14%)

Content Size

755.0 kB

After Optimization

652.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Namesbyorigin.com main page is 755.0 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. 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 315.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 96.7 kB

  • Original 118.2 kB
  • After minification 115.9 kB
  • After compression 21.5 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 96.7 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 4.9 kB

  • Original 315.8 kB
  • After minification 310.9 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. Names Byorigin images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 261 B

  • Original 199.8 kB
  • After minification 199.8 kB
  • After compression 199.5 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.

CSS Optimization

-0%

Potential reduce by 477 B

  • Original 121.1 kB
  • After minification 121.1 kB
  • After compression 120.7 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. Namesbyorigin.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

51

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

namesbyorigin.com

namesbyorigin.com

1259 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

242 ms

bootstrap.min.css

bootstrap.min.css

484 ms

font-sizes.min.css

font-sizes.min.css

696 ms

style.min.css

style.min.css

706 ms

all.min.css

all.min.css

714 ms

v4-shims.min.css

v4-shims.min.css

717 ms

clients-bar.css

clients-bar.css

723 ms

style.min.css

style.min.css

733 ms

css

css

29 ms

elementor-icons.min.css

elementor-icons.min.css

925 ms

frontend-legacy.min.css

frontend-legacy.min.css

939 ms

frontend.min.css

frontend.min.css

953 ms

post-408666.css

post-408666.css

949 ms

global.css

global.css

961 ms

post-14.css

post-14.css

974 ms

ninjatables-public.css

ninjatables-public.css

1158 ms

css

css

72 ms

jquery.min.js

jquery.min.js

1178 ms

jquery-migrate.min.js

jquery-migrate.min.js

1189 ms

adsbygoogle.js

adsbygoogle.js

385 ms

all.min.css

all.min.css

1193 ms

animations.min.css

animations.min.css

1199 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

1304 ms

comment-reply.min.js

comment-reply.min.js

1431 ms

bootstrap.min.js

bootstrap.min.js

1437 ms

core.min.js

core.min.js

1440 ms

script.min.js

script.min.js

1468 ms

footable.min.js

footable.min.js

1470 ms

ninja-tables-footable.3.1.0.js

ninja-tables-footable.3.1.0.js

1471 ms

webpack.runtime.min.js

webpack.runtime.min.js

1619 ms

frontend-modules.min.js

frontend-modules.min.js

1676 ms

waypoints.min.js

waypoints.min.js

1677 ms

swiper.min.js

swiper.min.js

1906 ms

share-link.min.js

share-link.min.js

1762 ms

dialog.min.js

dialog.min.js

1763 ms

frontend.min.js

frontend.min.js

1853 ms

preloaded-modules.min.js

preloaded-modules.min.js

1883 ms

css2

css2

12 ms

css2

css2

17 ms

gtm.js

gtm.js

173 ms

logo1-2.png

logo1-2.png

1171 ms

bg-02-3.jpg

bg-02-3.jpg

2135 ms

show_ads_impl.js

show_ads_impl.js

378 ms

zrt_lookup_nohtml.html

zrt_lookup_nohtml.html

32 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

22 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

46 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

62 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

62 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

103 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

59 ms

KFOlCnqEu92Fr1MmSU5fChc9.ttf

KFOlCnqEu92Fr1MmSU5fChc9.ttf

59 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

57 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

59 ms

KFOmCnqEu92Fr1Mu7GxP.ttf

KFOmCnqEu92Fr1Mu7GxP.ttf

102 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

103 ms

KFOlCnqEu92Fr1MmEU9fChc9.ttf

KFOlCnqEu92Fr1MmEU9fChc9.ttf

104 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

106 ms

KFOlCnqEu92Fr1MmWUlfChc9.ttf

KFOlCnqEu92Fr1MmWUlfChc9.ttf

106 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

105 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

104 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OmYWRm.ttf

104 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDIOmb2Rm.ttf

106 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoJYOmb2Rm.ttf

106 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOmb2Rm.ttf

107 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjovoSmb2Rm.ttf

108 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

108 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmYWRm.ttf

108 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

109 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoDISmb2Rm.ttf

110 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWmb2Rm.ttf

109 ms

fa-brands-400.woff

fa-brands-400.woff

1107 ms

js

js

49 ms

analytics.js

analytics.js

103 ms

collect

collect

13 ms

js

js

86 ms

ads

ads

341 ms

ninja-tables.woff

ninja-tables.woff

240 ms

ca-pub-5596957815771451

ca-pub-5596957815771451

100 ms

ads

ads

267 ms

Accessibility Review

namesbyorigin.com accessibility score

84

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

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

High

Links do not have a discernible name

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

namesbyorigin.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

namesbyorigin.com SEO score

100

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

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

namesbyorigin.com

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