12.7 sec in total
3.1 sec
9.3 sec
432 ms
Welcome to ifull.my homepage info - get ready to check IFull best content right away, or after learning these important things about ifull.my
Doorstep Instant Smartphones, iPad iPhone Repair Malaysia including Battery replacement, LCD screen repair.Trained Technician,Repair in 30min, No data loss.
Visit ifull.myWe analyzed Ifull.my page load time and found that the first response time was 3.1 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ifull.my performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value13.7 s
0/100
25%
Value17.2 s
0/100
10%
Value1,090 ms
24/100
30%
Value0.202
61/100
15%
Value12.0 s
16/100
10%
3064 ms
739 ms
496 ms
498 ms
8 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 81% of them (89 requests) were addressed to the original Ifull.my, 8% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Ifull.my.
Page size can be reduced by 318.7 kB (14%)
2.3 MB
1.9 MB
In fact, the total size of Ifull.my main page is 2.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 90.0 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 90.0 kB or 79% of the original size.
Potential reduce by 213.5 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, IFull needs image optimization as it can save up to 213.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 7.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. This website has mostly compressed JavaScripts.
Potential reduce by 8.3 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. Ifull.my has all CSS files already compressed.
Number of requests can be reduced by 81 (84%)
96
15
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IFull. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
ifull.my
3064 ms
style.min.css
739 ms
mainstyles.css
496 ms
styles.css
498 ms
jquery-ui.min.css
8 ms
jquery-ui-timepicker-addon.min.css
502 ms
settings.css
521 ms
reset.css
524 ms
superfish.css
743 ms
prettyPhoto.css
748 ms
jquery.qtip.css
755 ms
odometer-theme-default.css
781 ms
animations.css
784 ms
style.css
987 ms
css
16 ms
style.css
991 ms
responsive.css
997 ms
styles.css
1008 ms
styles.css
1041 ms
styles.css
1045 ms
styles.css
1238 ms
custom.css
1241 ms
js_composer.min.css
1751 ms
style.css
1264 ms
css
27 ms
css
29 ms
style.css
1301 ms
responsive.css
1305 ms
jquery.min.js
1730 ms
jquery-migrate.min.js
1490 ms
jquery.themepunch.tools.min.js
1521 ms
jquery.themepunch.revolution.min.js
1562 ms
js
59 ms
app.js
1323 ms
wp-polyfill-inert.min.js
1497 ms
regenerator-runtime.min.js
1570 ms
wp-polyfill.min.js
1672 ms
hooks.min.js
1598 ms
i18n.min.js
1774 ms
url.min.js
1775 ms
api-fetch.min.js
1775 ms
datepicker-en-GB.min.js
5 ms
index.js
1789 ms
core.min.js
1612 ms
datepicker.min.js
1652 ms
jquery-ui-timepicker-addon.min.js
1728 ms
jquery-ui-timepicker-en-GB.js
1722 ms
mouse.min.js
1731 ms
slider.min.js
1553 ms
controlgroup.min.js
1626 ms
checkboxradio.min.js
1664 ms
button.min.js
1725 ms
jquery-ui-sliderAccess.js
1712 ms
accordion.min.js
1728 ms
tabs.min.js
1561 ms
menu.min.js
1640 ms
selectmenu.min.js
1672 ms
jquery.ui.touch-punch.min.js
1718 ms
jquery.isotope.min.js
1700 ms
jquery.ba-bbq.min.js
1715 ms
jquery.easing.1.3.min.js
1566 ms
jquery.carouFredSel-6.2.1-packed.js
1656 ms
jquery.touchSwipe.min.js
1667 ms
jquery.transit.min.js
1671 ms
jquery.hint.min.js
1681 ms
jquery.qtip.min.js
1519 ms
jquery.blockUI.min.js
1534 ms
jquery.prettyPhoto.js
1595 ms
main.js
1627 ms
odometer.min.js
1521 ms
jquery.costCalculator.min.js
1513 ms
cost_calculator.js
1444 ms
js
104 ms
analytics.js
101 ms
js_composer_front.min.js
1468 ms
jquery-ui-tabs-rotate.min.js
1540 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
49 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
50 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
51 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
50 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
52 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
51 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
52 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
51 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
53 ms
forms.min.js
1524 ms
collect
17 ms
social.ttf
1449 ms
streamline-small.woff
1464 ms
streamline-large.woff
1489 ms
collect
24 ms
template.woff
1527 ms
v3.png
1042 ms
IFULL-WEB-BANNER-e1549904302739.png
3425 ms
1a-01-e1549905705654.png
4202 ms
iphone6-150x150.png
1076 ms
ipadpro10_wifigold-150x150.png
1306 ms
Huawei-Mate-9-150x150.png
1298 ms
DSC_0309-1-480x480.jpg
1522 ms
Artboard-1-90x90.png
1169 ms
Artboard-8-90x90.png
1332 ms
e1-01-e1549902879655.png
3228 ms
overlay.png
1173 ms
ui-bg_glass_65_ffffff_1x400.png
24 ms
preloader.gif
461 ms
ui-bg_glass_75_e6e6e6_1x400.png
5 ms
revolution.extension.slideanims.min.js
260 ms
revolution.extension.layeranimation.min.js
275 ms
revolution.extension.navigation.min.js
301 ms
loader.gif
254 ms
ifull.my 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
ifull.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ifull.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Ifull.my 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 Ifull.my 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.
ifull.my
Open Graph data is detected on the main page of IFull. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: