6.2 sec in total
1.6 sec
4.3 sec
281 ms
Click here to check amazing BIG content. Otherwise, check out these important facts you probably never knew about big.com.eg
barbary investment group, big, b.i.g, BIG,
Visit big.com.egWe analyzed Big.com.eg page load time and found that the first response time was 1.6 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
big.com.eg performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value9.9 s
0/100
25%
Value9.8 s
10/100
10%
Value450 ms
63/100
30%
Value0.028
100/100
15%
Value9.9 s
27/100
10%
1630 ms
209 ms
266 ms
252 ms
246 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 87% of them (58 requests) were addressed to the original Big.com.eg, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Big.com.eg.
Page size can be reduced by 981.4 kB (74%)
1.3 MB
338.4 kB
In fact, the total size of Big.com.eg main page is 1.3 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. 40% of websites need less resources to load. Javascripts take 915.0 kB which makes up the majority of the site volume.
Potential reduce by 46.4 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. This page needs HTML code to be minified as it can gain 13.9 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 46.4 kB or 82% of the original size.
Potential reduce by 57.6 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. Obviously, BIG needs image optimization as it can save up to 57.6 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 724.8 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 724.8 kB or 79% of the original size.
Potential reduce by 152.7 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. Big.com.eg needs all CSS files to be minified and compressed as it can save up to 152.7 kB or 74% of the original size.
Number of requests can be reduced by 38 (64%)
59
21
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BIG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
big.com.eg
1630 ms
language-selector.css
209 ms
style.css
266 ms
font-awesome.css
252 ms
navigation.css
246 ms
cms-navigation-base.css
248 ms
cms-navigation.css
410 ms
jquery.dataTables.css
437 ms
cf7msm.css
478 ms
styles.css
473 ms
dashicons.min.css
546 ms
thickbox.css
481 ms
front.css
629 ms
css
95 ms
default.min.css
644 ms
jquery.js
730 ms
jquery-migrate.min.js
704 ms
cf7msm.js
608 ms
jquery.bxSlider.min.js
756 ms
jquery.cycle.all.js
822 ms
jquery.prettyPhoto.js
829 ms
jquery.colorbox.js
854 ms
ddaccordion.js
913 ms
jquery.equalheights.js
936 ms
jquery.corner.js
962 ms
jquery.tools.tabs.min.js
1030 ms
functions.js
1030 ms
sitepress.js
1063 ms
prettyPhoto.css
1118 ms
colorbox.css
1135 ms
blue.css
1082 ms
custom_style.php
1403 ms
jquery.dataTables.JS
1726 ms
jquery.form.min.js
1272 ms
scripts.js
1292 ms
thickbox.js
1331 ms
jquery.cycle.all.min.js
1332 ms
highcharts.js
152 ms
reset.css
1231 ms
css
311 ms
loading2.gif
881 ms
top-glow.png
210 ms
ar.png
376 ms
en.png
214 ms
logo-big3211.jpg
229 ms
NILEX-new1.png
341 ms
egyptiansec.png
417 ms
footer-glow.png
324 ms
logo-big-grey.png
456 ms
facebook.jpg
524 ms
twitter.jpg
533 ms
feed.jpg
585 ms
linkedin.jpg
527 ms
controls.png
446 ms
border.png
524 ms
loading_background.png
531 ms
loading.gif
534 ms
loadingAnimation.gif
585 ms
slidenav-active.png
656 ms
slidenav.png
711 ms
wZLYhRRxZWGToTRP78bqJQ.woff
134 ms
UnXpojilM3XslYxUnWuVe_esZW2xOQ-xsNqO47m55DA.woff
169 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
221 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
236 ms
fontawesome-webfont.woff
798 ms
8ezAIdgyp-Cm5_X7mWzP_g.woff
234 ms
nr-892.min.js
40 ms
big.com.eg 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
big.com.eg 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
big.com.eg SEO score
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 Big.com.eg 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 Big.com.eg 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.
big.com.eg
Open Graph description is not detected on the main page of BIG. 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: