4.6 sec in total
127 ms
4.3 sec
162 ms
Welcome to origent.com homepage info - get ready to check Origent best content right away, or after learning these important things about origent.com
Visit origent.comWe analyzed Origent.com page load time and found that the first response time was 127 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
origent.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value20.1 s
0/100
25%
Value10.9 s
6/100
10%
Value0 ms
100/100
30%
Value0.057
98/100
15%
Value10.3 s
25/100
10%
127 ms
1261 ms
61 ms
107 ms
120 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 66% of them (38 requests) were addressed to the original Origent.com, 19% (11 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Origent.com.
Page size can be reduced by 1.5 MB (52%)
2.9 MB
1.4 MB
In fact, the total size of Origent.com main page is 2.9 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.1 MB which makes up the majority of the site volume.
Potential reduce by 55.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 55.5 kB or 80% of the original size.
Potential reduce by 65.7 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. Origent images are well optimized though.
Potential reduce by 412.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 412.5 kB or 70% of the original size.
Potential reduce by 968.6 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. Origent.com needs all CSS files to be minified and compressed as it can save up to 968.6 kB or 90% of the original size.
Number of requests can be reduced by 29 (66%)
44
15
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Origent. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
origent.com
127 ms
www.origent.com
1261 ms
mediaelementplayer-legacy.min.css
61 ms
wp-mediaelement.min.css
107 ms
styles.css
120 ms
front.min.css
132 ms
style.css
218 ms
css
56 ms
style-static.min.css
645 ms
style.css
165 ms
jquery.min.js
252 ms
jquery-migrate.min.js
173 ms
front.min.js
181 ms
ai.min.js
262 ms
js
101 ms
trackalyze.js
46 ms
index.js
225 ms
index.js
231 ms
dlm-xhr.min.js
269 ms
idle-timer.min.js
275 ms
custom.js
299 ms
scripts.min.js
401 ms
smoothscroll.js
310 ms
comment-reply.min.js
313 ms
common.js
317 ms
e-202420.js
39 ms
jquery.fitvids.js
369 ms
jquery.mobile.js
369 ms
style.css
198 ms
Origent-Logo-for-Banner-66h.png
67 ms
Origent-Logo.png
119 ms
BLANK.png
66 ms
geometic-background-origent-blue.jpg
118 ms
Origent-Logo-WHITE-for-banner.png
117 ms
font
172 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
174 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
585 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
600 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
601 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
600 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
594 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
596 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
596 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff
614 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
617 ms
modules.woff
169 ms
liveVisitAsync.js
564 ms
analytics.js
148 ms
shutterstock_72141592-1960wFADED50.jpg
677 ms
Origent-Logo-Wallpaper-GraySquare2.jpg
555 ms
ALS-Slider-Image.jpg
498 ms
Informed-Discovery.jpg
569 ms
Fail-Faster.jpg
557 ms
Invest-Confidently2.jpg
676 ms
tracking
78 ms
collect
20 ms
js
60 ms
style.min.css
103 ms
origent.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
origent.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
origent.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Origent.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 Origent.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.
origent.com
Open Graph description is not detected on the main page of Origent. 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: