2.4 sec in total
165 ms
1.8 sec
467 ms
Welcome to freshorigins.com homepage info - get ready to check Fresh Origins best content for United States right away, or after learning these important things about freshorigins.com
Fresh Origins Farm produces the very best MicroGreens, Petite MicroGreens, Edible Flowers and Crystallized Flowers. Please explore our site and discover the difference that Fresh Origins brings to the...
Visit freshorigins.comWe analyzed Freshorigins.com page load time and found that the first response time was 165 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
freshorigins.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value10.4 s
0/100
25%
Value8.2 s
20/100
10%
Value2,200 ms
6/100
30%
Value1.128
1/100
15%
Value13.5 s
11/100
10%
165 ms
178 ms
62 ms
74 ms
18 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 39% of them (29 requests) were addressed to the original Freshorigins.com, 20% (15 requests) were made to Scontent.cdninstagram.com and 13% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (653 ms) belongs to the original domain Freshorigins.com.
Page size can be reduced by 1.2 MB (38%)
3.2 MB
2.0 MB
In fact, the total size of Freshorigins.com main page is 3.2 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 48.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 48.3 kB or 79% of the original size.
Potential reduce by 37.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. Fresh Origins images are well optimized though.
Potential reduce by 800.1 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 800.1 kB or 72% of the original size.
Potential reduce by 357.5 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. Freshorigins.com needs all CSS files to be minified and compressed as it can save up to 357.5 kB or 84% of the original size.
Number of requests can be reduced by 21 (31%)
67
46
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fresh Origins. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
freshorigins.com
165 ms
autoptimize_a165e1c71940ef1200b9e9e6aeb517bf.css
178 ms
css
62 ms
css
74 ms
font-awesome.min.css
18 ms
all.js
33 ms
autoptimize_bc2f1882381fbef5f82234ba7869af9e.js
418 ms
ga.js
111 ms
logo.png
99 ms
loading.gif
141 ms
home2.jpg
140 ms
loading-white-bg.gif
140 ms
MicroGreens1-500x500.jpg
558 ms
transparent.png
135 ms
MicroGreenMixes1-500x500.jpg
530 ms
PetiteGreenMixes1-500x500.jpg
557 ms
PetiteGreenMixes-500x500.jpg
557 ms
shoots-500x500.jpg
556 ms
RelatedItems-500x500.jpg
529 ms
EdibleFlowers-500x500.jpg
599 ms
HerbCrystals-500x500.jpg
582 ms
482 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
457 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
457 ms
OpenSansBold-webfont.woff
649 ms
fontawesome-webfont.woff
43 ms
fontawesome-webfont.svg
653 ms
icomoon.woff
648 ms
xd_arbiter.php
39 ms
xd_arbiter.php
73 ms
__utm.gif
439 ms
__utm.gif
435 ms
10309062_10152430095995546_1315661713780848567_n.jpg
396 ms
widgets.js
255 ms
recent
593 ms
not.gif
204 ms
slider-fpo3-a.png
306 ms
slider-slide-2.jpg
203 ms
foss.jpg
235 ms
slider-fpo-e.jpg
240 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
40 ms
like_box.php
141 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
70 ms
410ucuAGgaJ.css
34 ms
tSbl8xBI27R.css
41 ms
1kPfZUdGrka.js
46 ms
Yuj_Y8xNH2C.js
64 ms
Mpe38fuBVZ2.js
63 ms
n8qIhCw3vMx.js
61 ms
fontawesome-webfont.woff
70 ms
10309062_10152430095995546_1315661713780848567_n.jpg
21 ms
wL6VQj7Ab77.png
5 ms
s7jcwEQH7Sx.png
5 ms
jot
109 ms
slider-arrows.png
58 ms
VXcANLwwL5J.js
19 ms
AmlxWlqMvlv.js
21 ms
slider-arrows-shadows.png
67 ms
OpenSans-Light-webfont.woff
75 ms
12407443_170062766698546_1785166604_n.jpg
178 ms
12063186_455864557934453_353083155_n.jpg
217 ms
12141822_1673196922922485_136430130_n.jpg
324 ms
12135213_1646587775566020_344678498_n.jpg
304 ms
11424576_421030908089591_986942229_n.jpg
304 ms
11327135_858955940856060_1665438231_n.jpg
301 ms
11374501_449912105182696_2052788487_n.jpg
306 ms
11375845_1599407133672227_1821177936_n.jpg
310 ms
11376276_975079629180791_1847871180_n.jpg
342 ms
11288005_849740535103729_1113064194_n.jpg
344 ms
10013302_752060821571518_1886018011_n.jpg
343 ms
11380977_1640256216197788_2082740512_n.jpg
399 ms
11420922_1639734686242355_418970000_n.jpg
349 ms
11313360_459134080920758_1540276597_n.jpg
363 ms
11372130_986479618051849_1355634602_n.jpg
382 ms
freshorigins.com
49 ms
freshorigins.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
freshorigins.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
freshorigins.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freshorigins.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 Freshorigins.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.
freshorigins.com
Open Graph data is detected on the main page of Fresh Origins. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: