6 sec in total
373 ms
5.2 sec
425 ms
Welcome to obor.it homepage info - get ready to check Obor best content right away, or after learning these important things about obor.it
Discover your premier destination for exceptional Italian lighting technology products. The blend of innovation and tradition today!
Visit obor.itWe analyzed Obor.it page load time and found that the first response time was 373 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
obor.it performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value42.4 s
0/100
25%
Value20.6 s
0/100
10%
Value410 ms
67/100
30%
Value0.803
5/100
15%
Value28.6 s
0/100
10%
373 ms
2515 ms
41 ms
381 ms
378 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 67% of them (64 requests) were addressed to the original Obor.it, 10% (10 requests) were made to Fonts.gstatic.com and 8% (8 requests) were made to S.w.org. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Obor.it.
Page size can be reduced by 1.1 MB (14%)
7.7 MB
6.6 MB
In fact, the total size of Obor.it main page is 7.7 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 6.4 MB which makes up the majority of the site volume.
Potential reduce by 148.2 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 148.2 kB or 81% of the original size.
Potential reduce by 84.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. Obor images are well optimized though.
Potential reduce by 470.0 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 470.0 kB or 71% of the original size.
Potential reduce by 401.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. Obor.it needs all CSS files to be minified and compressed as it can save up to 401.0 kB or 85% of the original size.
Number of requests can be reduced by 70 (84%)
83
13
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Obor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
obor.it
373 ms
2515 ms
analytics.js
41 ms
wp-emoji-release.min.js
381 ms
sbi-styles.min.css
378 ms
collect
12 ms
styles.css
282 ms
slick.min.css
294 ms
slick-theme.min.css
293 ms
exad-style.min.css
295 ms
wpfront-scroll-top.min.css
374 ms
elementor-icons.min.css
486 ms
frontend-legacy.min.css
488 ms
frontend.min.css
684 ms
post-2085.css
418 ms
all.min.css
513 ms
v4-shims.min.css
467 ms
global.css
512 ms
post-1472.css
562 ms
the-grid.min.css
679 ms
general.min.css
583 ms
front.css
606 ms
css
51 ms
jquery.min.js
698 ms
jquery-migrate.min.js
654 ms
v4-shims.min.js
680 ms
front.min.js
792 ms
uc.js
42 ms
css
50 ms
css
51 ms
css
48 ms
css
52 ms
style.css
745 ms
mobile.css
773 ms
slicknav.css
774 ms
jquery-1.10.2.min.js
40 ms
jquery.infinitescroll.js
774 ms
jquery.slicknav.js
788 ms
retina-1.1.0.min.js
883 ms
jquery.grid-a-licious.js
882 ms
modernizr-custom-v2.7.1.min.js
881 ms
jquery-finger-v0.1.0.min.js
881 ms
flickerplate.min.js
881 ms
flickerplate.css
882 ms
jquery.carouFredSel-6.2.1.js
994 ms
scripts.js
977 ms
animations.min.css
803 ms
index.js
708 ms
index.js
694 ms
slick.min.js
738 ms
exad-script.min.js
795 ms
wpfront-scroll-top.min.js
768 ms
effect.min.js
787 ms
the-grid.min.js
746 ms
general.min.js
673 ms
sbi-scripts.min.js
643 ms
webpack.runtime.min.js
687 ms
frontend-modules.min.js
689 ms
waypoints.min.js
668 ms
core.min.js
690 ms
swiper.min.js
747 ms
share-link.min.js
626 ms
dialog.min.js
660 ms
frontend.min.js
616 ms
preloaded-modules.min.js
692 ms
configuration.js
284 ms
cc.js
130 ms
css
79 ms
1f34f.svg
43 ms
logo3.png
420 ms
placeholder.png
426 ms
1.png
481 ms
1f49a.svg
43 ms
1f99a.svg
44 ms
1f338.svg
50 ms
1f335.svg
49 ms
1f64c-1f3fb.svg
47 ms
1f5a4.svg
49 ms
1f331.svg
46 ms
bc-v4.min.html
36 ms
FOTO-ARURORA-POLARE.jpg
553 ms
ACS_3193.jpg
681 ms
antonelli.jpg
709 ms
leone.jpg
707 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
59 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf
80 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMB.ttf
88 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf
91 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf
89 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf
90 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMB.ttf
89 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMB.ttf
87 ms
EYqxmaNOzLlWtsZSScy6XTNs.ttf
113 ms
fa-brands-400.woff
427 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
59 ms
jquery-1.10.2.min.js
3 ms
obor.it 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
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.
obor.it 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
obor.it SEO score
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 Obor.it 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 Obor.it 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.
obor.it
Open Graph description is not detected on the main page of Obor. 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: