Bery.No - Info bery.no

bery.no receives about 136 unique visitors and 408 (3.00 per visitor) page views per day which should earn about $1.67/day from advertising revenue. Estimated site value is $1,215.97. According to Alexa Traffic Rank bery.no is ranked number 5,776,300 in the world and 3.0E-6% of global Internet users visit it. Site is hosted in Norway and links to network IP address 91.242.200.159. This server doesn't support HTTPS and doesn't support HTTP/2.

About - bery.no


Technologies used on Website

JavaScript Libraries
FancyBox
jQuery
Analytics
Google Analytics
Font Scripts
Google Font API
Web Servers
Nginx
Reverse Proxy
Nginx

bery.no Profile

Last update was 42 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with bery.no in any way. Only publicly available statistics data are displayed.

How popular is bery.no?

136 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
136
Monthly Unique Visitors:
3,264
Pages per Visit:
3.00
Daily Pageviews:
408
Alexa Rank:
5,776,300 visit alexa
Alexa Reach:
3.0E-6%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  bery.no
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is bery.no?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
bery.no
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
bery.no
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much bery.no can earn?

Daily Revenue:
$1.67
Monthly Revenue:
$50.10
Yearly Revenue:
$609.55
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do bery.no lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is bery.no worth?

Website Value:
$1,215.97

+ Where is bery.no hosted?

Server IP:
91.242.200.159
ASN:
AS49788 
ISP:
Nexthop AS 
Server Location:

Norway, NO
 

Other sites hosted on 91.242.200.159

+ How fast does bery.no load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

97
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 320 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://www.bery.no/css/bery.css
4 KB70
http://www.bery.no/css/jquery.fancybox.css
2 KB110
http://www.bery.no/css/flexslider.css
2 KB110
http://www.bery.no/js/jquery.min.js
33 KB230
http://www.bery.no/js/jquery.fancybox.pack.js
6 KB150
http://www.bery.no/js/jquery.flexslider-min.js
5 KB110
http://www.bery.no/js/misc.js
2 KB70
http://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,600
1 KB190
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://bery.no/
0 ms126 ms0 KB0 KB301text/html
http://www.bery.no/
126 ms339 ms2 KB8 KB200text/htmlDocument
http://www.bery.no/css/bery.css
351 ms474 ms4 KB15 KB200text/cssStylesheet
http://www.bery.no/css/jquery.fancybox.css
351 ms476 ms2 KB9 KB200text/cssStylesheet
http://www.bery.no/css/flexslider.css
351 ms616 ms2 KB3 KB200text/cssStylesheet
http://www.bery.no/js/jquery.min.js
351 ms482 ms33 KB92 KB200application/javascriptScript
http://www.bery.no/js/jquery.fancybox.pack.js
352 ms497 ms6 KB16 KB200application/javascriptScript
http://www.bery.no/js/jquery.flexslider-min.js
352 ms611 ms5 KB17 KB200application/javascriptScript
http://www.bery.no/js/misc.js
352 ms477 ms2 KB5 KB200application/javascriptScript
http://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,600
352 ms382 ms1 KB9 KB200text/cssStylesheet
http://www.bery.no/bilder/bilder/custom/illu01.jpg
352 ms480 ms31 KB31 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/illu02.jpg
353 ms477 ms21 KB21 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/illu03.jpg
478 ms599 ms33 KB33 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/job.jpg
481 ms605 ms21 KB21 KB200image/jpegImage
http://www.google-analytics.com/ga.js
600 ms615 ms17 KB45 KB200text/javascriptScript
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=572977016&utmhn=www.bery.no&utmcs=UTF-8&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Bery%20Maritime%20AS&utmhid=153076848&utmr=-&utmp=%2F&utmht=1575991945910&utmac=UA-1398274-8&utmcc=__utma%3D165657900.1482035525.1575991946.1575991946.1575991946.1%3B%2B__utmz%3D165657900.1575991946.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=386834321&utmredir=1&utmu=qAEAAAAAAAAAAAAAAAAAAAAE~
670 ms674 ms0 KB0 KB200image/gifImage
http://www.bery.no/bilder/bilder/custom/logo.png
684 ms811 ms5 KB5 KB200image/pngImage
http://www.bery.no/bilder/bilder/custom/slide01.jpg
685 ms923 ms223 KB223 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/slide02.jpg
685 ms818 ms166 KB166 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/slide03.jpg
685 ms937 ms283 KB282 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/slide04.jpg
686 ms932 ms268 KB267 KB200image/jpegImage
http://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN_r8OUuhp.woff2
688 ms693 ms15 KB15 KB200font/woff2Font
http://fonts.gstatic.com/s/opensans/v17/mem8YaGs126MiZpBA-UFVZ0b.woff2
690 ms693 ms14 KB14 KB200font/woff2Font
http://fonts.gstatic.com/s/opensans/v17/memnYaGs126MiZpBA-UFUKWyV9hrIqM.woff2
691 ms695 ms14 KB14 KB200font/woff2Font
http://browser-update.org/update.js
941 ms967 ms4 KB9 KB200application/javascriptScript
Serve static assets with an efficient cache policy - 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.bery.no/bilder/bilder/custom/slide03.jpg
0 ms283 KB
http://www.bery.no/bilder/bilder/custom/slide04.jpg
0 ms268 KB
http://www.bery.no/bilder/bilder/custom/slide01.jpg
0 ms223 KB
http://www.bery.no/bilder/bilder/custom/slide02.jpg
0 ms166 KB
http://www.bery.no/bilder/bilder/custom/illu03.jpg
0 ms33 KB
http://www.bery.no/js/jquery.min.js
0 ms33 KB
http://www.bery.no/bilder/bilder/custom/illu01.jpg
0 ms31 KB
http://www.bery.no/bilder/bilder/custom/illu02.jpg
0 ms21 KB
http://www.bery.no/bilder/bilder/custom/job.jpg
0 ms21 KB
http://www.bery.no/js/jquery.fancybox.pack.js
0 ms6 KB
http://www.bery.no/js/jquery.flexslider-min.js
0 ms5 KB
http://www.bery.no/bilder/bilder/custom/logo.png
0 ms5 KB
http://www.bery.no/css/bery.css
0 ms4 KB
http://www.bery.no/css/jquery.fancybox.css
0 ms2 KB
http://www.bery.no/js/misc.js
0 ms2 KB
http://www.bery.no/css/flexslider.css
0 ms2 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
http://browser-update.org/update.js
86400000 ms4 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
18 KB0 ms
4 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
367 ms
8 ms
642 ms
18 ms
664 ms
32 ms
698 ms
76 ms
787 ms
8 ms
976 ms
12 ms
995 ms
8 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN_r8OUuhp.woff2
5 ms
http://fonts.gstatic.com/s/opensans/v17/mem8YaGs126MiZpBA-UFVZ0b.woff2
3 ms
http://fonts.gstatic.com/s/opensans/v17/memnYaGs126MiZpBA-UFUKWyV9hrIqM.woff2
4 ms
JavaScript execution time - 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
http://www.bery.no/js/jquery.min.js
164 ms123 ms3 ms
Other
141 ms4 ms1 ms
Properly size images - Potential savings of 74 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://www.bery.no/bilder/bilder/custom/illu03.jpg
33 KB23 KB
http://www.bery.no/bilder/bilder/custom/illu01.jpg
31 KB22 KB
http://www.bery.no/bilder/bilder/custom/illu02.jpg
21 KB15 KB
http://www.bery.no/bilder/bilder/custom/job.jpg
21 KB15 KB
Avoids enormous network payloads - Total size was 1,174 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.bery.no/bilder/bilder/custom/slide03.jpg
283 KB
http://www.bery.no/bilder/bilder/custom/slide04.jpg
268 KB
http://www.bery.no/bilder/bilder/custom/slide01.jpg
223 KB
http://www.bery.no/bilder/bilder/custom/slide02.jpg
166 KB
http://www.bery.no/bilder/bilder/custom/illu03.jpg
33 KB
http://www.bery.no/js/jquery.min.js
33 KB
http://www.bery.no/bilder/bilder/custom/illu01.jpg
31 KB
http://www.bery.no/bilder/bilder/custom/illu02.jpg
21 KB
http://www.bery.no/bilder/bilder/custom/job.jpg
21 KB
http://www.google-analytics.com/ga.js
17 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
170 ms
Other
73 ms
Style & Layout
54 ms
Rendering
39 ms
Script Parsing & Compilation
9 ms
Parse HTML & CSS
9 ms
Serve images in next-gen formats - Potential savings of 112 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://www.bery.no/bilder/bilder/custom/slide02.jpg
166 KB75 KB
http://www.bery.no/bilder/bilder/custom/illu01.jpg
31 KB12 KB
http://www.bery.no/bilder/bilder/custom/job.jpg
21 KB9 KB
http://www.bery.no/bilder/bilder/custom/illu02.jpg
21 KB8 KB
http://www.bery.no/bilder/bilder/custom/illu03.jpg
33 KB8 KB
Avoids an excessive DOM size - 106 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
106
Maximum DOM Depth
9
Maximum Child Elements
5
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://bery.no/)
0
http://www.bery.no/
190
Keep request counts low and transfer sizes small - 25 requests • 1,174 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
251174 KB
Image
101051 KB
Script
668 KB
Font
343 KB
Stylesheet
49 KB
Document
12 KB
Other
10 KB
Media
00 KB
Third-party
766 KB
Server response times are low (TTFB) - Root document took 210 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 10 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

92
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 5033.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 3.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 106 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
106
Maximum DOM Depth
9
Maximum Child Elements
5
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://bery.no/)
0
http://www.bery.no/
630
Keep request counts low and transfer sizes small - 25 requests • 1,157 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
251157 KB
Image
111058 KB
Script
668 KB
Font
219 KB
Stylesheet
49 KB
Document
12 KB
Other
10 KB
Media
00 KB
Third-party
642 KB
Eliminate render-blocking resources - Potential savings of 1,510 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://www.bery.no/css/bery.css
4 KB180
http://www.bery.no/css/jquery.fancybox.css
2 KB330
http://www.bery.no/css/flexslider.css
2 KB330
http://www.bery.no/js/jquery.min.js
33 KB930
http://www.bery.no/js/jquery.fancybox.pack.js
6 KB480
http://www.bery.no/js/jquery.flexslider-min.js
5 KB480
http://www.bery.no/js/misc.js
2 KB180
http://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,600
1 KB630
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://bery.no/
0 ms245 ms0 KB0 KB301text/html
http://www.bery.no/
246 ms419 ms2 KB8 KB200text/htmlDocument
http://www.bery.no/css/bery.css
430 ms561 ms4 KB15 KB200text/cssStylesheet
http://www.bery.no/css/jquery.fancybox.css
431 ms556 ms2 KB9 KB200text/cssStylesheet
http://www.bery.no/css/flexslider.css
431 ms552 ms2 KB3 KB200text/cssStylesheet
http://www.bery.no/js/jquery.min.js
431 ms793 ms33 KB92 KB200application/javascriptScript
http://www.bery.no/js/jquery.fancybox.pack.js
432 ms553 ms6 KB16 KB200application/javascriptScript
http://www.bery.no/js/jquery.flexslider-min.js
432 ms670 ms5 KB17 KB200application/javascriptScript
http://www.bery.no/js/misc.js
432 ms557 ms2 KB5 KB200application/javascriptScript
http://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,600
433 ms451 ms1 KB10 KB200text/cssStylesheet
http://www.bery.no/bilder/bilder/custom/illu01.jpg
433 ms677 ms31 KB31 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/illu02.jpg
433 ms663 ms21 KB21 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/illu03.jpg
664 ms901 ms33 KB33 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/job.jpg
678 ms803 ms21 KB21 KB200image/jpegImage
http://www.google-analytics.com/ga.js
816 ms821 ms17 KB45 KB200text/javascriptScript
http://www.bery.no/bilder/bilder/custom/logo_x2.png
829 ms953 ms9 KB9 KB200image/pngImage
http://www.bery.no/bilder/bilder/struktur_element/meny.png
830 ms953 ms2 KB2 KB200image/pngImage
http://www.bery.no/bilder/bilder/custom/slide01.jpg
830 ms1199 ms223 KB223 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/slide02.jpg
830 ms1314 ms166 KB166 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/slide03.jpg
831 ms1200 ms283 KB282 KB200image/jpegImage
http://www.bery.no/bilder/bilder/custom/slide04.jpg
831 ms1549 ms268 KB267 KB200image/jpegImage
http://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN_r8OUuhpKKSTjw.woff2
833 ms837 ms9 KB9 KB200font/woff2Font
http://fonts.gstatic.com/s/opensans/v17/memnYaGs126MiZpBA-UFUKWyV9hrIqOxjaPX.woff2
835 ms839 ms10 KB10 KB200font/woff2Font
http://www.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=949909095&utmhn=www.bery.no&utmcs=UTF-8&utmsr=412x660&utmvp=412x660&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Bery%20Maritime%20AS&utmhid=2007253007&utmr=-&utmp=%2F&utmht=1575991936302&utmac=UA-1398274-8&utmcc=__utma%3D165657900.1375554331.1575991936.1575991936.1575991936.1%3B%2B__utmz%3D165657900.1575991936.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=2095395244&utmredir=1&utmu=qAEAAAAAAAAAAAAAAAAAAAAE~
918 ms922 ms0 KB0 KB200image/gifImage
http://browser-update.org/update.js
1552 ms1571 ms4 KB9 KB200application/javascriptScript
Serve static assets with an efficient cache policy - 19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://www.bery.no/bilder/bilder/custom/slide03.jpg
0 ms283 KB
http://www.bery.no/bilder/bilder/custom/slide04.jpg
0 ms268 KB
http://www.bery.no/bilder/bilder/custom/slide01.jpg
0 ms223 KB
http://www.bery.no/bilder/bilder/custom/slide02.jpg
0 ms166 KB
http://www.bery.no/bilder/bilder/custom/illu03.jpg
0 ms33 KB
http://www.bery.no/js/jquery.min.js
0 ms33 KB
http://www.bery.no/bilder/bilder/custom/illu01.jpg
0 ms31 KB
http://www.bery.no/bilder/bilder/custom/illu02.jpg
0 ms21 KB
http://www.bery.no/bilder/bilder/custom/job.jpg
0 ms21 KB
http://www.bery.no/bilder/bilder/custom/logo_x2.png
0 ms9 KB
http://www.bery.no/js/jquery.fancybox.pack.js
0 ms6 KB
http://www.bery.no/js/jquery.flexslider-min.js
0 ms5 KB
http://www.bery.no/css/bery.css
0 ms4 KB
http://www.bery.no/bilder/bilder/struktur_element/meny.png
0 ms2 KB
http://www.bery.no/css/jquery.fancybox.css
0 ms2 KB
http://www.bery.no/js/misc.js
0 ms2 KB
http://www.bery.no/css/flexslider.css
0 ms2 KB
http://www.google-analytics.com/ga.js
7200000 ms17 KB
http://browser-update.org/update.js
86400000 ms4 KB
Minimize third-party usage - Third-party code blocked the main thread for 50 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
18 KB48 ms
4 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
446 ms
7 ms
455 ms
6 ms
825 ms
16 ms
846 ms
52 ms
904 ms
8 ms
916 ms
27 ms
1598 ms
6 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://fonts.gstatic.com/s/opensans/v17/mem5YaGs126MiZpBA-UN_r8OUuhpKKSTjw.woff2
4 ms
http://fonts.gstatic.com/s/opensans/v17/memnYaGs126MiZpBA-UFUKWyV9hrIqOxjaPX.woff2
4 ms
JavaScript execution time - 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
596 ms13 ms4 ms
http://www.bery.no/js/jquery.min.js
563 ms436 ms10 ms
http://www.google-analytics.com/ga.js
108 ms101 ms5 ms
Avoids enormous network payloads - Total size was 1,157 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://www.bery.no/bilder/bilder/custom/slide03.jpg
283 KB
http://www.bery.no/bilder/bilder/custom/slide04.jpg
268 KB
http://www.bery.no/bilder/bilder/custom/slide01.jpg
223 KB
http://www.bery.no/bilder/bilder/custom/slide02.jpg
166 KB
http://www.bery.no/bilder/bilder/custom/illu03.jpg
33 KB
http://www.bery.no/js/jquery.min.js
33 KB
http://www.bery.no/bilder/bilder/custom/illu01.jpg
31 KB
http://www.bery.no/bilder/bilder/custom/illu02.jpg
21 KB
http://www.bery.no/bilder/bilder/custom/job.jpg
21 KB
http://www.google-analytics.com/ga.js
17 KB
Minimizes main-thread work - 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
594 ms
Other
297 ms
Style & Layout
200 ms
Rendering
165 ms
Parse HTML & CSS
34 ms
Script Parsing & Compilation
33 ms
Garbage Collection
2 ms
Serve images in next-gen formats - Potential savings of 112 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://www.bery.no/bilder/bilder/custom/slide02.jpg
166 KB75 KB
http://www.bery.no/bilder/bilder/custom/illu01.jpg
31 KB12 KB
http://www.bery.no/bilder/bilder/custom/job.jpg
21 KB9 KB
http://www.bery.no/bilder/bilder/custom/illu02.jpg
21 KB8 KB
http://www.bery.no/bilder/bilder/custom/illu03.jpg
33 KB8 KB
Avoid chaining critical requests - 9 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 170 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://www.bery.no/js/jquery.min.js
http://www.bery.no/js/jquery.fancybox.pack.js
http://www.bery.no/js/jquery.flexslider-min.js
http://www.bery.no/js/misc.js
Optimize CSS Delivery of the following:

http://www.bery.no/css/bery.css
http://www.bery.no/css/jquery.fancybox.css
http://www.bery.no/css/flexslider.css
http://fonts.googleapis.com/css?family=Open+Sans:400,300,300italic,600

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.bery.no/bilder/bilder/custom/illu01.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/custom/illu02.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/custom/illu03.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/custom/job.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/custom/logo_x2.png (expiration not specified)
http://www.bery.no/bilder/bilder/custom/slide01.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/custom/slide02.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/custom/slide03.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/custom/slide04.jpg (expiration not specified)
http://www.bery.no/bilder/bilder/struktur_element/meny.png (expiration not specified)
http://www.bery.no/css/bery.css (expiration not specified)
http://www.bery.no/css/flexslider.css (expiration not specified)
http://www.bery.no/css/jquery.fancybox.css (expiration not specified)
http://www.bery.no/js/jquery.fancybox.pack.js (expiration not specified)
http://www.bery.no/js/jquery.flexslider-min.js (expiration not specified)
http://www.bery.no/js/jquery.min.js (expiration not specified)
http://www.bery.no/js/misc.js (expiration not specified)
http://www.google-***ytics.com/ga.js (2 hours)

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="contact-us">Contact us</a> and 2 others are close to other tap targets.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 12.5KiB (15% reduction).

Compressing http://www.bery.no/bilder/bilder/custom/illu01.jpg could save 4.2KiB (14% reduction).
Compressing http://www.bery.no/bilder/bilder/custom/illu02.jpg could save 3.5KiB (17% reduction).
Compressing http://www.bery.no/bilder/bilder/custom/job.jpg could save 2.3KiB (11% reduction).
Compressing http://www.bery.no/bilder/bilder/custom/logo_x2.png could save 1.4KiB (16% reduction).
Compressing http://www.bery.no/bilder/bilder/struktur_element/meny.png could save 1.1KiB (50% reduction).

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 1.5KiB (21% reduction).

Minifying http://www.bery.no/css/jquery.fancybox.css could save 545B (26% reduction) after compression.
Minifying http://www.bery.no/css/bery.css could save 525B (14% reduction) after compression.
Minifying http://www.bery.no/css/flexslider.css could save 429B (33% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 4***B (27% reduction).

Minifying http://www.bery.no/js/misc.js could save 4***B (27% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 332B (17% reduction).

Minifying http://www.bery.no/ could save 332B (17% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does bery.no use compression?

bery.no use gzip compression.
Original size: 8.27 KB
Compressed size: 1.98 KB
File reduced by: 6.28 KB (76%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

bery.no does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

bery.no does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Tue, 10 Dec 2019 15:32:03 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 300
Connection: keep-alive
Location: http://www.bery.no/

HTTP/1.1 200 OK
Server: nginx
Date: Tue, 10 Dec 2019 15:32:04 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 2031
Connection: keep-alive
X-Server: MacGyver
X-Current-Server: Gleeson
Set-Cookie: AWA_start_2019=iu7jccl1bjunc5usrck2645nd0; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
A 91.242.200.159 267
SOA 3600
Mname ns1.hyp.net
Rname hostmaster.domeneshop.no
Serial Number 1574200336
Refresh 14400
Retry 3600
Expire 777600
Minimum TTL 0
NS ns3.hyp.net 3567
NS ns2.hyp.net 3567
NS ns1.hyp.net 3567

+ Whois Lookup

Domain Created:
1999-11-15
Domain Age:
20 years 25 days  
WhoIs:
 

whois lookup at whois.norid.no...
% By looking up information in the domain registration directory
% service, you confirm that you accept the terms and conditions of the
% service:
% https://www.norid.no/en/domeneoppslag/vilkar/
%
% Norid AS holds the copyright to the lookup service, content,
% layout and the underlying collections of information used in the
% service (cf. the Act on Intellectual Property of May 2, 1961, No.
% 2). Any commercial % use of information from the service, including
% targeted marketing, is prohibited. Using information from the domain
% registration directory service in % violation of the terms and
% conditions may result in legal prosecution.
%
% The whois service at port 43 is intended to contribute to resolving
% technical problems where individual domains threaten the
% functionality, security and stability of other domains or the
% internet as an infrastructure. It does not give any information
% about who the holder of a domain is. To find information about a
% domain holder, please visit our website:
% https://www.norid.no/en/domeneoppslag/

Domain Information

NORID Handle...............: BER4299D-NORID
Domain Name................: bery.no
Registrar Handle...........: REG42-NORID
Tech-c Handle..............: DH38R-NORID
Name Server Handle.........: NSHY11H-NORID
Name Server Handle.........: NSHY46H-NORID
Name Server Handle.........: NSHY81H-NORID
DNSSEC.....................: Signed
DS Key Tag 1...........: 56480
Algorithm 1...........: 13
Digest Type 1...........: 2
Digest 1...........: 6d7adc9a624b5400fb9ea11deb93535e25ed1223f26068b29708b5d27b9a2e8f

Additional information:
Created: 1999-11-15
Last updated: 2019-10-15
Last update was 42 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with bery.no in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

ttor.org
4 secs
ttisi.com
51 secs
tsunamidemocratic.github.io
2 mins
birminghamlive.co.uk
2 mins
tsuhomecoming.com
2 mins
tsstudio.org
4 mins
tsoutsoura.com
5 mins
bitlylink.com
5 mins
supercoder.com
5 mins
tsmeventservices.com
5 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
bery.no widget