3.2 sec in total
752 ms
2.2 sec
230 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 752 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
origent.com performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value16.4 s
0/100
25%
Value19.0 s
0/100
10%
Value260 ms
83/100
30%
Value0.018
100/100
15%
Value17.4 s
4/100
10%
752 ms
133 ms
25 ms
262 ms
38 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 71% of them (35 requests) were addressed to the original Origent.com, 14% (7 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to T2.trackalyzer.com. The less responsive or slowest element that took the longest time to load (752 ms) belongs to the original domain Origent.com.
Page size can be reduced by 949.9 kB (46%)
2.1 MB
1.1 MB
In fact, the total size of Origent.com main page is 2.1 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.
Potential reduce by 29.3 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 29.3 kB or 79% of the original size.
Potential reduce by 78.1 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 336.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 336.5 kB or 77% of the original size.
Potential reduce by 506.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. Origent.com needs all CSS files to be minified and compressed as it can save up to 506.0 kB or 89% of the original size.
Number of requests can be reduced by 24 (60%)
40
16
The browser has sent 40 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 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.origent.com
752 ms
wp-emoji-release.min.js
133 ms
css
25 ms
style.css
262 ms
css
38 ms
style.css
90 ms
shortcodes.css
136 ms
magnific_popup.css
92 ms
jquery.js
382 ms
jquery-migrate.min.js
140 ms
ai.js
194 ms
trackalyze.js
238 ms
frontend-builder-global-functions.js
128 ms
idle-timer.min.js
135 ms
custom.js
125 ms
comment-reply.min.js
160 ms
jquery.mobile.custom.min.js
169 ms
custom.js
215 ms
smoothscroll.js
182 ms
jquery.fitvids.js
207 ms
waypoints.min.js
215 ms
jquery.magnific-popup.js
227 ms
frontend-builder-scripts.js
329 ms
wp-embed.min.js
249 ms
style.css
456 ms
Origent-Logo-for-Banner-66h.png
55 ms
ALS-Slider-Image.jpg
221 ms
Origent-Logo-Wallpaper-GraySquare2.jpg
178 ms
Origent-Logo.png
178 ms
Informed-Discovery.jpg
185 ms
Fail-Faster.jpg
178 ms
Invest-Confidently2.jpg
185 ms
BLANK.png
181 ms
hex-bg-29290a-for-naturebiotech.jpg
184 ms
NatureBiotech.jpg
181 ms
geometic-background-origent-blue.jpg
220 ms
Origent-Logo-WHITE-for-banner.png
185 ms
trackalyze.asp
153 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
13 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
14 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
24 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
24 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
24 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
24 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
24 ms
ETmodules_v2_4.ttf
239 ms
liveVisitAsync.js
150 ms
dot.gif
76 ms
ProcessStats.aspx
37 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
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: